My feeling is that neither JDK 5 or 6 should exhibit this behavior. I
have an app that is deployed under JDK6 that typically has 50 concurrent
users hitting it every 30 secs 24x7 and I don't see this sort of issue.
The only problem I've had is growth in the PermGen pool which eventually
can cause an out of permgen exception, but that's after at least a
couple of weeks, and does not exhibit as a freeze-up.
When you say it gets 'stuck', for how long does it get stuck?
Out of interest, are you using the client or the server vm?
Could this just be a GC tuning issue? The client VM could spend a lot of
time doing a garbage collect. How much RAM do you have in the machine,
and how big is the Java heap? (-mx)
Janne Jalkanen wrote:
On 29 Mar 2008, at 03:47, Milton Taylor wrote:
Janne - what evidence do you have that Java 6 is not as stable as
1.5? What kind of stability are you referrring to? ..Milt
jspwiki.org sometimes experiences very high-load conditions (load
20++). Java 5 seems to handle these better, whereas Java 6 gets stuck
in them for much longer periods of time. During this time, the server
is unresponsive. We have a shell script which reaps stuck Tomcats and
restarts the container.
With JDK6, these restarts occur about daily. With Java 5, the
restarts occur every four-five days.
/Janne
