Our JBoss Appserver is using Port 8009. I can only use a port once on the
same machine. So the port seems not to be the problem.

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

Do you have a tip about this?

By the way, thanx for your hint :-)

Markus

-----Ursprungliche Nachricht-----
Von: Chris Wilkes [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 11. Juli 2003 14:37
An: [EMAIL PROTECTED]
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:11:25PM +0200, Markus Heussen wrote:
>
> I've the configuration as subject on my Win 2K Server. I use Apache 2 on
> Port 80 to serve the static content and mod_jk2 over AJP13 on Port 8010
> installed as Apache Module to serve the dynamic Tomcat content. Tomcat is
> listening on this Port to serve the Cocoon 2 servlet.

Where did you get port 8010?  I have it working fine on my two boxes and
its on port 8009.

Not that there's anything wrong with running it on that port, but it
seems a bit odd.

Chris

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to