I am experiencing something very strange, that I don't even know how to debug.

We run apache+mod_ssl-1.3.34+2.8.25_2, jakarta-tomcat-5.0.30 and mod_jk-1.2.15,1 on FreeBSD 6.1-amd64, and it is really rock stable.

Now, into this picture comes a helix server (aka Real server, real media server). Support for FreeBSD is rather poor, so we run an old binary, version built for FreeBSD 5.x-x86 (SERVER_10_1_STABLE branch,

With it comes the problems. When the helix server is running, the apache<-mod_jk->tomcat connection (tcp/ip on localhost using the AJP13 protocol, btw) gets into trouble, resulting in error 500 to the user fetching the web page.

At first I thought the system was somehow exhausted of resources, but no other logs complain about that. The mod_jk log reports:

[Mon Jan 08 15:12:43 2007] [error] ajp_service::jk_ajp_common.c (1758): Error connecting to tomcat. Tomcat is probably not started or is listening on the wrong port. worker=tomcat failed [Mon Jan 08 15:12:43 2007] [error] ajp_connection_tcp_get_message::jk_ajp_common.c (961): Can't receive the response message from tomcat, network problems or tomcat is down (, err=-54 [Mon Jan 08 15:12:43 2007] [error] ajp_get_reply::jk_ajp_common.c (1503): Tomcat is down or refused connection. No response has been sent to the client (yet)

Has anyone seen anything like this before. Is anyone running the helix server on FreeBSD?

Palle Girgensohn <[EMAIL PROTECTED]>

freebsd-questions@freebsd.org mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to