We're updating the issue view to help you get more done. 

The cargo:run goal in combination with starting a debugger fails to shut down cleanly

Description

When you use the cargo:run goal and specify the jvmargs configuration property to start a debugger:

1 2 3 <cargo.jvmargs> <![CDATA[-Xdebug -Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=n -noverify]]> </cargo.jvmargs>

then when you ctrl-c to shut down the process you get the following error:

1 2 3 4 [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]

Probably cargo starts up a new JVM to initiate the shutdown with the same JVM arguments as specified for starting the container.

Status

Assignee

Savas Ali Tokmen

Reporter

S. Ali Tokmen

Components

Fix versions

Affects versions

1.4.7

Priority

Major