You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some time between 1.0.1 and 1.1.1, run-jetty-run would inconsistently crash
when trying to debug a project.
Most of the time it's a full on JVM crash, not some sort of Exception.
Other times it gets "stuck" and has to be killed.
What steps will reproduce the problem?
1. Create a web project (in this case it's a fairly complex project using
Tapestry, Hibernate and Spring.
2. Add a breakpoint
3. Trigger breakpoint and boom
What is the expected output? What do you see instead?
I expect to be able to debug my app instead of Jetty crashing.
What version of the product are you using? On what operating system?
run-jetty-run 1.1.1, Fedora 10, Eclipse 3.4.1
Please provide any additional information below.
Depending on the break point, it doesn't seem to always crash immediately.
Some times I have to step through the code to get it to crash.
I've tried uninstalling/reinstalling, removing all break points, creating a
fresh Debug configuration with the same results.
Going back to 1.0.1 and everything works fine.
Original issue reported on code.google.com by dree...@gmail.com on 7 May 2009 at 11:54
The text was updated successfully, but these errors were encountered:
rjr is a pure java app (in fact, it is just a couple of classes in the runtime
process; the rest is jetty and your app). I can't immediately imagine what rjr
could
be doing that would trigger a jvm crash, but it almost certainly implies a jvm
bug.
I do understand that upgrading from 1.0.1 to 1.1.1 trigger the bug, but I'm
doubtful
that it is rjr's "fault".
I suggest you report this to sun as a jvm bug, and include the dump that the
jvm
should be writing out at the time of the crash.
Original comment by James.Sy...@gmail.com on 16 May 2009 at 2:56
Changed title: Sun JRE 1.6.0_13-b03 crashes on breakpoints with run-jetty-run version 1.1.1
Original issue reported on code.google.com by
dree...@gmail.com
on 7 May 2009 at 11:54The text was updated successfully, but these errors were encountered: