Eclipse Jetty JDK6 debug - JVM Hault

 

Recently I was involved in developing a web application using Tapestry 5 web framework. The Eclipse IDE (Ganymede in this particular) was setup to use JDK6 and the application server was Jetty running through run-jetty-run Eclipse plugin.

For reasons unknow while debuging the application at some point the JVM just kept on crashing with a message that can be seen below:

 

---------------  T H R E A D  ---------------

Current thread (0x0cac6400):  VMThread [stack: 0x0cb50000,0x0cba0000]
[id=4068]

Stack: [0x0cb50000,0x0cba0000]
[error occurred during error reporting (printing stack bounds), id
0x80000001]

VM_Operation (0x0f27e0b4): GenCollectForAllocation, mode: safepoint,
requested by thread 0x0dca8000

 

After spending few restart I have noticed that this is a systematic crash. It seems that the cause of this crash is the placement of breakpoint that inside methods that are annotated.

So in order to avoid this crash you need to remove all breakpoint from the methods that have annotations on them. I know that this is annoying but there seems to be no other way.

Hope this will save you some time.

This page was last updated on: 10/06/2010 06:46