When this error happens, are you able to issue the command
1. to see if tomcat is listening,
netstat -na |grep 8009 |grep LISTEN
2. if yes, try to connect to the socket
"telnet localhost 8009"
on the box you see the error, this will tell you if the server socket is
alright.
Fillip
Randy Pa
Filip
The Both the apache and tomcat are on the same server and the
workers.properties connects via localhost
Thanks
On 2/13/06, Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote:
> Hi Randy, if Apache cannot talk to Tomcat, then its not because of the
> clustering. The first error in catalina.o
Hi Randy, if Apache cannot talk to Tomcat, then its not because of the
clustering. The first error in catalina.out, is just a result of
replication keep alive sessions getting closed, I will fix the code that
generates that error so that it doesn't log as an error.
do you have a firewall or any
s there any firewall between
> > > the apache and your tomcat server? Or did your IT dept reconfigure the
> > > network recently?
> > >
> > > ND
> > >
> > > -Original Message-
> > > From: Randy Paries [mailto:[EMAIL PROTECTED]
>
tween
> > the apache and your tomcat server? Or did your IT dept reconfigure the
> > network recently?
> >
> > ND
> >
> > -Original Message-
> > From: Randy Paries [mailto:[EMAIL PROTECTED]
> > Sent: Monday, February 13, 2006 9:27 AM
> >
MAIL PROTECTED]
> Sent: Monday, February 13, 2006 9:27 AM
> To: Tomcat Users List
> Subject: problems with Clusters or apache connector not sure which one
>
> hello,
> I am running apache-tomcat-5.5.15 on three boxes 2 rh9 and one fedora
> 4. and they are clustered together
>
&
List
Subject: problems with Clusters or apache connector not sure which one
hello,
I am running apache-tomcat-5.5.15 on three boxes 2 rh9 and one fedora
4. and they are clustered together
I am seeing problems where apache can not longer talk to tomcat.
if anyone can point me on how to debug this
hello,
I am running apache-tomcat-5.5.15 on three boxes 2 rh9 and one fedora
4. and they are clustered together
I am seeing problems where apache can not longer talk to tomcat.
if anyone can point me on how to debug this please help, i am not sure
what else i should include as far a conf setups,