cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Markus Heussen" <heus...@rheinland-online.com>
Subject AW: Apache 2.0.44 + Tomcat 4.1.25 + mod_jk2-2.0.43 + Cocoon 2.0.4
Date Mon, 14 Jul 2003 09:57:07 GMT
Thanx for your help, Chris.

The problem was our proxy and/or firewall servers (miss)configuration. On
the local machine I have no problems and from an other lan it works also
fine. So everything works fine now - Thank God!  :-)

I even have the message

[INFO] ChannelSocket - -Connection timeout reached

in my Tomcat error log. But it seems that this causes no furhter problems to
the application. The Apache error log is clean now.

Greetins

Markus



-----Ursprungliche Nachricht-----
Von: Chris Wilkes [mailto:cwilkes-cocoon@ladro.com]
Gesendet: Freitag, 11. Juli 2003 17:06
An: users@cocoon.apache.org
Betreff: Re: Apache 2.0.44 + Tomcat 4.1.25 + mod_jk2-2.0.43 + Cocoon
2.0.4


(note: top posting makes it hard to follow a thread)

> -----Ursprungliche Nachricht-----
> Von: Chris Wilkes [mailto:cwilkes-cocoon@ladro.com]
> Gesendet: Freitag, 11. Juli 2003 15:10
> An: users@cocoon.apache.org
> Betreff: Re: Apache 2.0.44 + Tomcat 4.1.25 + mod_jk2-2.0.43 + Cocoon
> 2.0.4
>
>
> On Fri, Jul 11, 2003 at 02:48:52PM +0200, Markus Heussen wrote:
> >
> > I've crasy error messages in the apache logs. something like the
following
> > is printed out after the second request that is routed to tomcat:
> >
> >
> > [error] ChannelSocket.receive(): Error receiving message body -1 0
> > [error] workerEnv.processCallbacks() Error reading reply
> > [error] ajp13.service() ajpGetReply recoverable error 120000
> >
> > And so on. But the Apache 2 is receiving a response from tomcat, but
> > with a scaring performance.
> >
> > Also the Tomcat logs throw error. stderror.log contains
> > something like this after the second request:
> >
> > [INFO] JKMain - -Jk running ID=0 time=0/15
> > config=D:\APPSERVER\tomcat41\conf\jk2.properties
> > [INFO] ChannelSocket - -Connection timeout reached
> > [INFO] ChannelSocket - -Connection timeout reached
> > [INFO] ChannelSocket - -Connection timeout reached
>
> Are you using Tomcat 4.1.25?  The latest stable release is 4.1.24, you
> might want to try and use that.  Did you use the binary release from the
> Jakarta site?
On Fri, Jul 11, 2003 at 03:14:44PM +0200, Markus Heussen wrote:
> That's my fault. We are using 4.1.24 win32 binaries. Sorry ;-)

Do you have a weird workers.properties file?

It might be helpful to do a tcpdump / tethereal of the port 8010 traffic
and see if there's anything in there that points to a problem.

This post on the Tomcat mailing list has a similiar error:
  http://marc.theaimsgroup.com/?l=tomcat-user&m=105471584215995&w=2

Chris

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org


Mime
View raw message