Hello...
First I would like to say how impressed I am with Grizzly. Great job!
However, on one of our client systems we are having a performance issue that
occurs approximately every hour and can last up to ten minutes. When this
happens Java takes 100% of the CPU and the garbage collect starts thrashing.
Attached is the output from the HP JMeter statistics gathered on the system
as well as stack dumps taken during the performance problem.
I've seen a couple of posts where Grizzly seems to be stuck in preClose0,
but I don't see how that was ever resolved. The stack traces attached show
this is a likely scenario.
We are using grizzly web server 1.9.18-e with one selector thread and 30
maximum worker threads. The client's system is a two CPU system with 14
gigs (we have Java configured to 1/2 gig initial and max). Bumping the
initial/max to one gig did not make a difference.
Java version 1.5.0.18
HP-UX OS version B.11.11
Any help would be greatly appreciated.
Thanks!
--dennis
http://old.nabble.com/file/p26733514/consecutive_sigquit_121009.txt
consecutive_sigquit_121009.txt
http://old.nabble.com/file/p26733514/GC.jpeg
--
View this message in context: http://old.nabble.com/Grizzly-Web-Server-on-HP-UX-PA-RISC-Performance-Issue-tp26733514p26733514.html
Sent from the Grizzly - Users mailing list archive at Nabble.com.
