-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jordan,
On 2/15/2010 6:24 PM, Jordan Michaels wrote: > The client got in touch with us today stating that the entire site was > now unresponsive. We reviewed the log files and miraculously this time > there WAS an error message (lots of them). > > The error was as follows: > ----------- > SEVERE: Error allocating socket processor > java.lang.OutOfMemoryError: unable to create new native thread That'll do it. > So, looking at my setenv.sh values, it turns out that Xss256m is > extremely massive. Hah, yeah. I didn't notice that on first reading. > I reduced the > value to 512k, and things are now working beautifully. I would leave the stack size to the default, unless you see a need to increase it. You might also want to review your nominal thread count in the JVM: it's possible that you are getting close to the limit of threads for a process in your environment. > I can only guess at why there were no logs when this happened previously > (maybe no memory left to spawn a new logging thread? no idea...), but > the page that was hanging now runs very quickly even when I hammer my > refresh button on it. =D Try ApacheBench... it's a much better hammer. Good luck, - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkt7FYYACgkQ9CaO5/Lv0PB8dQCcDNkl0DCH05Jic0IhnpTUHzKv prIAnRN1eBhNiWYvqUgsDnfXbK8Ckevq =3v5F -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
