Bug 290066

Description Robert Brown III 2009-09-21 15:45:22 EDT

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.11) Gecko/2009061118 Fedora/3.0.11-1.fc9 Firefox/3.0.11
Build Identifier: 20090621-0832

Whenever someone attempts to run or debug an application running under Glassfish, the server starts up without problems, but some time after the deployment the Eclipse Servers tab shows that the server has stopped. In reality it has not; after Eclipse tells you that it has stopped you can actually start up a browser and use the server. Note that because Eclipse "thinks" the server has stopped you cannot run debugging sessions or run any application from Eclipse.

Because Eclipse "thinks" that the application has stopped, attempts to start it again generate an error (Port is in use failure). Then you have to stop the server from Eclipse and start it again in order to get it to deploy any changes you made in your code.

This only occurs under Linux. Under Windows this does not occur.


Reproducible: Always

Steps to Reproduce:
1. Create a Web Application project that runs under Glassfish
2. Write some code (servlet, JSP, whatever).
3.Run the Glassfish server either in "run" or "debug" mode
4. After Glassfish starts up, wait a few seconds. Eclipse will tell you that Glassfish has stopped
5. When Eclipse tells you Glassfish has stopped, start up a browser and go to http://localhost:8080, http://localhost:4848, or to the URL where your application is deployed (http://localhost:8080/yourapp). You will find that Glassfish is actually running!

6. Make some changes in the code
7. Attempt to run Glassfish again. You will get a failure saing the port is in use.Your "stop" button will then be enabled
8. Click the "stop" button. Sometimes the server stops, sometimes it displays a dialog saying that the server isn't responding. If the latter happens, click OK to stop the server

9. The server will be start- able again.