Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Trivial Trivial
    • Resolution: Fixed
    • Affects Version/s: 0.9.0
    • Fix Version/s: 0.9.3
    • Component/s: Maven Launcher
    • Labels:
      None
    • Environment:
      Windows XP, Eclipse 3.3.2
    • Number of attachments :
      0

      Description

      When i execute clean package on a 1600+ classes project i get this error almost in every build

      [INFO] ------------------------------------------------------------------------
      [INFO] BUILD SUCCESSFUL
      [INFO] ------------------------------------------------------------------------
      [INFO] Total time: 2 minutes 3 seconds
      [INFO] Finished at: Thu Mar 13 10:48:14 EDT 2008
      [INFO] Final Memory: 4M/80M
      [INFO] ------------------------------------------------------------------------
      JDWP exit error JVMTI_ERROR_WRONG_PHASE(112): on getting class statusJDWP exit error JVMTI_ERROR_INVALID_ENVIRONMENT(116): Can't allocate jvmti memoryERROR: JDWP unable to dispose of JVMTI environment: JVMTI_ERROR_INVALID_ENVIRONMENT(116) ["debugInit.c",L388]
      FATAL ERROR in native method: JDWP Can't allocate jvmti memory, jvmtiError=JVMTI_ERROR_INVALID_ENVIRONMENT(116)

        Issue Links

          Activity

          Hide
          Eugene Kuleshov added a comment -

          I see this occasionally too. It happens when debugged JVM exists and generally is harmless.

          Show
          Eugene Kuleshov added a comment - I see this occasionally too. It happens when debugged JVM exists and generally is harmless.
          Hide
          Eugene Kuleshov added a comment -

          Fixed as part of MNGECLIPSE-548. Now "Run As... / Maven..." is not starting external JVM in debugger and in order to debug you would have to use corresponding "Debug As... / Maven..." actions, so reported issue is not relevant anymore for regular Maven execution.

          Show
          Eugene Kuleshov added a comment - Fixed as part of MNGECLIPSE-548 . Now "Run As... / Maven..." is not starting external JVM in debugger and in order to debug you would have to use corresponding "Debug As... / Maven..." actions, so reported issue is not relevant anymore for regular Maven execution.

            People

            • Assignee:
              Eugene Kuleshov
              Reporter:
              Francisco Herrera
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: