Hi again,
After some weeks, Mr. Hanik help us solving the problem.
And he found it!
The problem was the sticky sessions, and our balancer: pen.
Pen, (http://siag.nu/pen/) it's a simple load balancer, and it doesn't care
about sessions between nodes.
That provokes dead locks at tomcat.
The proble
className="org.apache.catalina.tribes.group.interceptors.MessageDispatch15In
terceptor"/>
className="org.apache.catalina.tribes.group.interceptors.ThroughputIntercept
or"/>
filter=".*\.gif;.*\.js;.*\.jpg;.*\.png;.*\.htm;.*\.html;.*\.css;.*\.t
nce.
Raúl.
-Mensaje original-
De: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED]
Enviado el: lunes, 28 de enero de 2008 1:45
Para: Tomcat Users List
Asunto: Re: Tomcat 6 - Cluster error.
I'd set keepAliveTime to 10 as well,
Filip
Raúl García wrote:
> Hi Again, once again thanks
Mensaje original-
De: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED]
Enviado el: jueves, 17 de enero de 2008 19:01
Para: Tomcat Users List
Asunto: Re: Tomcat 6 - Cluster error.
already replied to your old thread
ok, it looks like you might have ended up with a rogue socket,
and what
---Mensaje original-
De: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED]
Enviado el: jueves, 17 de enero de 2008 19:01
Para: Tomcat Users List
Asunto: Re: Tomcat 6 - Cluster error.
already replied to your old thread
ok, it looks like you
García [mailto:[EMAIL PROTECTED]
Enviado el: viernes, 18 de enero de 2008 11:23
Para: 'Tomcat Users List'
Asunto: RE: Tomcat 6 - Cluster error.
Hi Filip,
Thank you for that suggestion. We are going to try it now.
On the other side, if You want to reproduce the error:
We have used a
ECTED]
Enviado el: viernes, 18 de enero de 2008 11:23
Para: 'Tomcat Users List'
Asunto: RE: Tomcat 6 - Cluster error.
Hi Filip,
Thank you for that suggestion. We are going to try it now.
On the other side, if You want to reproduce the error:
We have used a server here configured with t
01
Para: Tomcat Users List
Asunto: Re: Tomcat 6 - Cluster error.
already replied to your old thread
ok, it looks like you might have ended up with a rogue socket,
and what happens is that any message sent to that socket just gets lost
in the ether, since it doesn't have any interest ops.
Th
already replied to your old thread
ok, it looks like you might have ended up with a rogue socket,
and what happens is that any message sent to that socket just gets lost
in the ether, since it doesn't have any interest ops.
There is a workaround for this, turn off keep alives all together, or
i
Hi,
I repost the problem with a better subject:
We had a tomcat 5.0.28 server configured with 2 clustered instances(working
perfectly), and we decided to migrate to java6 and the new tomcat 6.0.14.
We modified the configuration files to match the new tomcat 6.0.14
structure.
But now we have reall
10 matches
Mail list logo
