Re: apache2, mod_jk2, tomcat4.1.27: "server has been restarted orreset this connection"

[Jeff Tulley <JT...@novell.com>]

I've seen it on other OS's.  Well, the one I develop for, at least --
NetWare.  We are using Apache 2.x, mod_jk, and Tomcat 4.1.18 (happens in
4.1.27 too, I think).

I don't run enough serious apps on Windows to know if it happens there
as well.  My guess is that it would.

Jeff Tulley  (jtulley@novell.com)
(801)861-5322
Novell, Inc., The Leading Provider of Net Business Solutions
http://www.novell.com

>>> eric@iCky.org 8/26/03 11:34:47 AM >>>
Hi,

I get this too.

You can add a connectionTimeout to the Connector (I use 120000) and
you
will no longer get a "reset" INFO message but a "connection timed out"
INFO message.

I know that it is possible for the user to get a 400 or 500 error due
to
these resets.  I haven't ran a test with the timeout settings to find
out.
I have done it with the timeout set to 0 (the default).

Also what OS are you using?  We spoke about this before and it seemed
to
be unique to Solaris.  Linux didn't have the problem.

But no one has figured out an answer to it...  at least that I know
of.

-e

On Tue, 26 Aug 2003, Chris Joelly wrote:

> Hello again!
>
> anybody any idea about this behavior?
>
> thx, Chris
>
> Am Wed, Aug 20, 2003 at 03:42:55PM +0200, Chris Joelly meinte:
> >
> > i have setup apache2 with mod_jk2 and tomcat4.1.27 and all works
fine,
> > but the following log messages is written to the mod_jk log file:
> >
> > 19.08.2003 16:43:05 org.apache.jk.common.ChannelSocket
processConnection
> > INFO: server has been restarted or reset this connection
> > 19.08.2003 16:43:05 org.apache.jk.common.ChannelSocket
processConnection
> > INFO: server has been restarted or reset this connection
> > 19.08.2003 16:43:05 org.apache.jk.common.ChannelSocket
processConnection
> > INFO: server has been restarted or reset this connection
> > 19.08.2003 16:43:05 org.apache.jk.common.ChannelSocket
processConnection
> >
> > as i can see this log message is written on every request, so i
can
> > change the log level or if there is a real problem would
appreciate
> > solving the problem.
> >
> > is this a real problem? and if yes, does anybody know whats the
problem?
> > i have tried several things with WORKER.sockt_keepalive and
> > WORKER.socket_timeout, but things don't change...
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org 
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org

>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org 
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org