search

wjw465150 / run-jetty-run

Automatically exported from code.google.com/p/run-jetty-run
0 stars 0 forks source link

Exception "lost connection with Eclipse" when leaving Jetty running overnight and coming back the next morning #170

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What is the expected output? What do you see instead?

I upgraded to the latest nightly build (1.3.3.201301020723) and now when I 
leave Jetty 8 running overnight and I come back the next morning, I see the 
exception "lost connection with Eclipse , shutting down.".  This is a 
regression from the previous build with Jetty 8.

What steps will reproduce the problem?

1. Install nightly build and start Jetty 9.

2. Come back the next morning.

EXPECTING: Jetty should still be running.

ACTUAL: Jetty is not running.  In the Console output, I see the following: lost 
connection with Eclipse , shutting down.

What Eclipse version are you using ?

Version: Juno Service Release 2
Build id: 20130225-0426

What Run-Jetty-Run version are you using?

  RunJettyRun Jetty9 Support (Optional) 1.3.3.201301020723

What OS are you using ? 32bit or 64 bit?

- OS X 10.7.5

Please provide any additional information below.

Would it be possible to change the nightly build to output the full exception 
in Bootstrap.java and then I can provide additional details?  Thanks!

Original issue reported on code.google.com by joshung...@gmail.com on 7 Jun 2013 at 3:00

GoogleCodeExporter commented 9 years ago 
I am seeing the same issue, but with different versions of things:

* RunJettyRun 1.3.3.201203161919,
* Jetty 8.1.2.v20120308
* Eclipse 3.8.2
* Oracle JRE 1.7.0_40 64-bit
* Ubuntu 12.04, 64-bit

I recently switched from a Oracle JRE 1.6 to Oracle JRE 1.7, and I don't recall 
seeing this problem with JRE 1.6. May or may not be coincidence ... I might be 
able to switch back and try 1.6 again.

Original comment by stacktra...@gmail.com on 30 Sep 2013 at 11:42

GoogleCodeExporter commented 9 years ago 
Tried it overnight with Oracle JRE 1.6.0_32 64-bit, and had the same issue. So 
I guess it has nothing to do with Java 7.

Original comment by stacktra...@gmail.com on 1 Oct 2013 at 11:51

GoogleCodeExporter commented 9 years ago 
got the same problem.

nobody knows the cause of it?

Original comment by streul...@gmail.com on 16 Oct 2013 at 6:53