Thankyou very much for your diagnosis here, Mark. I will investigate the
proposed solution and let you know how it goes.
Cheers,
Matt.
-Original Message-
From: Mark Thomas [mailto:ma...@apache.org]
Sent: Tuesday, 20 July 2010 3:07 AM
To: Tomcat Users List
Subject: Re: SEVERE message
May be, but i do notthink so.
This errors :
SEVERE: Manager [localhost#/urs]: Unable to receive message through TCP
channel
java.lang.
IllegalStateException: removeAttribute: Session already
invalidated
may dependds on tomcat failure
and i see in the Receiver configuration:
Receiver ...
On 19/07/2010 10:50, Luciano Fioriti wrote:
May be, but i do notthink so.
Again, you are way off-base here. Hitting the max threads in the
connector has nothing to do with errors in session replication.
Mark
This errors :
SEVERE: Manager [localhost#/urs]: Unable to receive message through
On 16/07/2010 10:19, Mark Thomas wrote:
On 16/07/2010 06:49, Matt Peterson wrote:
While load testing our clustered Tomcats, we are seeing the following
stack
trace in our catalina.out occasionally, but not regularly:
Jul 16, 2010 3:34:49 PM org.apache.catalina.ha.session.DeltaManager
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark,
On 7/19/2010 1:07 PM, Mark Thomas wrote:
Testing shows that it is caused by using async session replication. If
you use synchronous replication that ensures messages are processed on
the receiving nodes in the order they are sent.
On 19/07/2010 22:36, Christopher Schultz wrote:
Mark,
On 7/19/2010 1:07 PM, Mark Thomas wrote:
Testing shows that it is caused by using async session replication. If
you use synchronous replication that ensures messages are processed on
the receiving nodes in the order they are sent.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark,
On 7/19/2010 6:00 PM, Mark Thomas wrote:
On 19/07/2010 22:36, Christopher Schultz wrote:
Mark,
On 7/19/2010 1:07 PM, Mark Thomas wrote:
Testing shows that it is caused by using async session replication. If
you use synchronous replication
On 16/07/2010 06:49, Matt Peterson wrote:
While load testing our clustered Tomcats, we are seeing the following stack
trace in our catalina.out occasionally, but not regularly:
Jul 16, 2010 3:34:49 PM org.apache.catalina.ha.session.DeltaManager
messageReceived
SEVERE: Manager
It may be caused by maxThreads parameter in http connector, try to increase
lucio
2010/7/16 Mark Thomas ma...@apache.org
On 16/07/2010 06:49, Matt Peterson wrote:
While load testing our clustered Tomcats, we are seeing the following
stack
trace in our catalina.out occasionally, but not
On 16/07/2010 14:19, Luciano Fioriti wrote:
It may be caused by maxThreads parameter in http connector, try to increase
On what basis are you reaching that conclusion?
Mark
lucio
2010/7/16 Mark Thomasma...@apache.org
On 16/07/2010 06:49, Matt Peterson wrote:
While load testing our
I had done a stress test with 20 contemporary request to a web app using
tomcat6 6bit.
When maxThreads=200 tomcat gave response to only some request then went to
0 cpu time
no more response, nothing on log file.
This happenend only on contemporary requests (max threads reched i presume).
could you someone please help me?
I need to know what is the end of life for Apache tomcat 5.5.28 and 5.5.29.
I would appreciate anyone's help
Thank you,
-Nejet
On Fri, Jul 16, 2010 at 9:19 AM, Luciano Fioriti lu.fior...@gmail.comwrote:
It may be caused by maxThreads parameter in http
nejet erradi wrote:
could you someone please help me?
I need to know what is the end of life for Apache tomcat 5.5.28 and 5.5.29.
I would appreciate anyone's help
Thank you,
-Nejet
1) do not hijack threads
2) see http://tomcat.apache.org/whichversion.html
On 16/07/2010 14:50, Luciano Fioriti wrote:
I had done a stress test with 20 contemporary request to a web app using
tomcat6 6bit.
When maxThreads=200 tomcat gave response to only some request then went to
0 cpu time
no more response, nothing on log file.
This happenend only on contemporary
14 matches
Mail list logo
