Most times when I attempt to stop WEBrick, using either the x in the bottom right of the screen or the Servers node, the
server fails to stop. The first time I click the x, I'm asked if I want to stop WEBrick. Once I say yes, any further
clicks on the x do nothing. I then have to kill the Java process to kill the server, then the running status bar goes
away. What other information can I provide to help troubleshoot this issue?
Which build are you using? JRuby/Ruby? I'll try to reproduce on Mac, haven't seen this myself on Linux.
6.1 Beta. It also appears to work OK for me on Windows. Note, I can stop the server after immediately starting it. It's
only after it's up and running for a bit when this occurs. But it has affected everyone of my Ruby demos, where I need
to restart the server because of Java libraries I've added. If you want to go through those steps yourself, they're here:
followed by (it's this 2nd demo that requires the restart. You don't actually have to do the demo - just try to stop the
server after doing the demo above.)
I just experienced this on Solaris x86 testing the RoR Hands On Lab for JavaOne
I have noticed this as well in Gentoo Linux. Using NB 6.1 I can't get WEBrick to stop in the IDE or when the IDE is shut
I added some logging to track down the problem, could try with the latest build with Ruby logging enabled and attach the
log file here then when this happens again? The params to enable logging are:
BTW, does this happen with JRuby only?
Created attachment 60067 [details]
Log File with additional logging enabled
Doesn't seem very helpful, the but the log's attached:
INFO [org.netbeans.modules.ruby.platform.execution.OutputForwarder]: Process finished unexpectedly: Stream closed
Created attachment 60068 [details]
I've also attached a tread dump which should highlight the problem.
"DestroyJavaVM" prio=5 tid=0x01001a10 nid=0xb0801000 waiting on condition [0x00000000..0xb0800060]
Thanks. Seems that this could be an issue in JRuby, or have you run into this when using MRI? I'll still investigate
and file an issue against JRuby if needed, will also look at whether there is something that could be done on the IDE
You may be right. I've been using MRI of late and I haven't run into the problem.
*** Issue 133470 has been marked as a duplicate of this issue. ***
I think this was related to a bug in JRuby 1.1, should be fixed in later releases (I recall seeing an issue on this,
but can't find it now -- I'll post a link here if I find it). So I'm closing this, please reopen if this happens to you
again with a newer JRuby.