Page Comparison

...

Note

title	About the cargo.start.jvmargs property

The JVM start arguments configuration property only exists since Codehaus Cargo 1.4.18.

With older versions, you'll have to use cargo.jvmargs and make sure you set the execution property only on the start goal - Else you will get error messages such as:

Code Block
[INFO] [talledLocalContainer] FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)


[WARNING] [talledLocalContainer] ERROR: transport error 202: bind failed: Address already in use


[WARNING] [talledLocalContainer] ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)


[WARNING] [talledLocalContainer] JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:741]

Redirecting container output to a file and setting the log level of the container

...

Versions Compared

Old Version 46

New Version Current

Key

Redirecting container output to a file and setting the log level of the container