Periodically, I'm getting problems with my Tomcat 6 cluster (2 nodes). One
of the nodes would just go haywire and generate a ton of logs repeating the
following:
Aug 25, 2009 11:44:10 AM org.apache.catalina.ha.session.DeltaRequest reset
SEVERE: Unable to remove element
CS Wong schrieb:
Periodically, I'm getting problems with my Tomcat 6 cluster (2 nodes).
One of the nodes would just go haywire
Could you elaborate on what going haywire means?
Below, you write:
[The NoSuchElementException is] the only thing that it shows. The
other node in the cluster is
Hi Michael,
The logs are the bit that went haywire. The applications at this point still
work but often, there's not enough time to troubleshoot much else. The logs
can increase by 5-6GB in a matter of an hour or so and hence, we often just
kill the service (normal shutdown.sh doesn't respond any
what version of Tomcat, and we will get it fixed
On 08/25/2009 12:22 AM, CS Wong wrote:
Periodically, I'm getting problems with my Tomcat 6 cluster (2 nodes). One
of the nodes would just go haywire and generate a ton of logs repeating the
following:
Aug 25, 2009 11:44:10 AM
I've taken a look at the code.
The fix for this is easy, but it doesn't explain why it happens. This is
a concurrency issue, but if you're not running the latest tomcat
version, then it could already have been fixed.
best
Filip
On 08/25/2009 01:55 AM, CS Wong wrote:
Hi Michael,
The logs are
Thanks, Filip.
I'm running 6.0.14 right now. Would you have any idea whether any changes in
the code since then would have fixed something like this? I can try to push
for an upgrade to 6.0.20 but the app owners would probably want to know
whether it would be fixed for sure since they have to go
A brief look through svn log
http://svn.apache.org/repos/asf/tomcat/trunk/java/org/apache/catalina/ha/session/DeltaRequest.java;
turns up this:
r618823 | fhanik | 2008-02-06 07:29:56 +0800 (Wed, 06 Feb 2008) | 3 lines
Remove
hi Wong, yes, that one does implement a higher level of thread safety,
and most likely would resolve your problem.
With 6.0.20, there is a regression where tomcat nodes on the same host
wont discover each other
https://issues.apache.org/bugzilla/show_bug.cgi?id=47308
Filip
On 08/25/2009 07:22
ok, we'll try this out then.
One question about the regression, would it occur if the 2 nodes are in
different Solaris containers (both having different IPs) but on the same
physical host?
Thanks a lot!
Wong
On Wed, Aug 26, 2009 at 10:39 AM, Filip Hanik - Dev Lists
devli...@hanik.com wrote:
