Hi,
We have a Glassfish V2 UR2 Server running on Windows 2003 Server (I know,.. not the best, but you work with what you have!)
I've just put our new website beta, and redirected some of our traffic onto it (approx 40 visitors per second). The site is using JSP, with EJB and a connection to a remote RMI application.
It started, that every hour or so, the website would slow down, and eventually stop answering requests to the http listener. The https listener was still ok however.
I would then restart glassfish, and it would come up again without a problem, run for about an hour, and then crash.
I have read through lots of the threads on this subject, and have done the following things:
I have set the JVM-Options:
-server
-Dcom.sun.enterprise.server.ss.ASQuickStartup=false
-Dcom.sun.enterprise.web.connector.useCoyoteConnector=true
These were not all turned on at the same time but have each helped a little. The largest stability increase was after setting useCoyoteConnector=true. Setting this however did start to throw up exceptions in the server log on startup. Probably because certain aspects of glassfish is only supported by grizzly (or so I have read).
I also set the acceptor threads to 8.
We are using a SQL Server 2005 DB, and after reading on another forum about SQL Login Timeout problems, I added the loginTimeout=10 to the JDBC connection pool.
The server now runs for about 3 or 4 hours without crashing, but can sometimes last a lot longer.
During the last crash, I grabbed a JStack (attached), an there appears to be plenty of locks in there.
Is there anyone out there who can point me in the right direction. This is very important, and I'm very close to ditching glassfish in favour of tomcat...
Thanks,
Adam
[Message sent by forum member 'adamburrett' (adamburrett)]
http://forums.java.net/jive/thread.jspa?messageID=278803