Where before the server stopped responding within a few hours it has run for maybe 18 hours now without problem. This is after adding the Coyote JVM option below:
-Dcom.sun.enterprise.web.connector.useCoyoteConnector=true
I would not yet call this conclusive. I think I should leave it running for several days.
I also used ulimit to increase the number of allowable open files from 1024 to 8192, like so:
ulimit -n 8192.
I did this because I was seeing "too many open files" exceptions on my server. The server is an Amazon EC2 instance running Ubuntu that hits S3 frequently. I believe this error to be unrelated to the unresponsive server issue because I was seeing the server stop responding on both machines that were experiencing the "too many open files" exceptions and those that were not.
[Message sent by forum member 'kevinmacdonald' (kevinmacdonald)]
http://forums.java.net/jive/thread.jspa?messageID=272391