I had seen this build failures in my dev env. For me, the problem went
away after reboot, so I assumed Windows and/or JVM accumulated some odd
state. I do not think this has much to do with JDT debug, though.
Eugene Kuleshov wrote:
So far I only seen this error happening when Maven process was
finishing. In that case this error can be ignored. Please let us know if
this error is happening in a middle of build and cause termination of
Maven process.
I opened bug on Eclipse JDT/Debug about this. You can cc yourself at
https://bugs.eclipse.org/bugs/show_bug.cgi?id=224806
regards,
Eugene
Igor Fedorenko wrote:
Does this happen every time you launch maven build or only
occasionally? I've opened an improvement request to make debugging of
external maven builds optional
(http://jira.codehaus.org/browse/MNGECLIPSE-539).
If you see this error every time you run maven build, please open new
bugreport with project and steps to reproduce the problem.
http://docs.codehaus.org/display/M2ECLIPSE/Reporting+Issues
youhaodeyi wrote:
I use Eclipse 3.3.2, jdk1.6.0_03 and Maven 2.0.7 and got this error when
compiling source code:
FATAL ERROR in native method: JDWP on raw monitor enter,
jvmtiError=JVMTI_ERROR_INVALID_ENVIRONMENT(116)
JDWP exit error JVMTI_ERROR_WRONG_PHASE(112): on getting class status
[../../../src/share/back/util.c:1265]
JDWP exit error JVMTI_ERROR_INVALID_ENVIRONMENT(116): on raw monitor
enter
[../../../src/share/back/util.c:1034]
ERROR: JDWP unable to dispose of JVMTI environment:
JVMTI_ERROR_INVALID_ENVIRONMENT(116)
How can I fix it?
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
