Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sun JRE 1.6.0_13-b03 crashes on breakpoints with run-jetty-run version 1.1.1 #30

Closed
GoogleCodeExporter opened this issue Jul 7, 2015 · 3 comments

Comments

@GoogleCodeExporter
Copy link

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

@GoogleCodeExporter
Copy link
Author

Which JVM are you using?

Original comment by James.Sy...@gmail.com on 8 May 2009 at 2:16

@GoogleCodeExporter
Copy link
Author

java version "1.6.0_13"
Java(TM) SE Runtime Environment (build 1.6.0_13-b03)
Java HotSpot(TM) Server VM (build 11.3-b02, mixed mode)

Original comment by dree...@gmail.com on 8 May 2009 at 5:29

@GoogleCodeExporter
Copy link
Author

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
  • Changed state: Invalid

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant