Uploaded image for project: 'Codehaus Cargo'
  1. CARGO-1263

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

    Details

    • Type: Bug
    • Status: Closed (View workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects versions: 1.4.7
    • Fix versions: 1.4.8
    • Components: Maven2/Maven3
    • Labels:
      None

      Description

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

      <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:

      [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.

        Attachments

          Activity

            People

            • Assignee:
              Savas Ali Tokmen (Inactive)
              Reporter:
              S. Ali Tokmen
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: