fyi, I built this tcnative using the latest APR src libraries 1.2.12, if that
helps.
ewsinc wrote:
Hi,
I have Tomcat 6.0.14 running fine with mod_jk and Apache 2.2.
When I place tcnative library path in the java library path, then the
catalina.out log starts/stops at below:
Dec 7
I have had the same question without any answer from this forum.
You can turn on mod_jk logging to see what the httpd side of the ajp
protocol has to say.
I got those errors to go away, but I don't know how to turn on detailed
logging for the tomcat side of ajp
I am unable to find any error
... I will try getting
the latest mod_jk and see if they work better with the latest APR libs.
ewsinc wrote:
found the problem ... it was SELinux disabling access to the
jk-runtime-status file...
which mod_jk wanted to access at startup of httpd/mod_jk.
ewsinc wrote:
I see
the latest mod_jk.1.22 doesn't seem to improve things with APR connector, as
indicated by the Tomcat Manager.
So for now, I have kept the libtcnative out of the Tomcat deployment.
ewsinc wrote:
not quite. other errors remain complaining about sockets not open:
[Sat May 12 22:47:34 2007
as I reported in another post here, the resolution was removing the APR
connector (libtcnative) and using the standard AJP connector not sure
why this is so, but now I see many threads opened and remaining open in the
Tomcat Manager.
ewsinc wrote:
I am running tomcat 6.0.10 on RHEL4
I see in the Manager/status page an error count under the AJP-8009 section of
the page.
How do I go and find out what those errors are?
How does one turn on logging for AJP?
I have logging turned on for mod_jk in Apache... but what about logging for
Tomcat's side of the AJP protocol?
--
View
I had this same problem ... see recent post about tracing down errors in the
ajp-8009 part of the manager/status page... well... it was SELinux... after
checking below, and googling around, I come to suspect SELinux... I did a
setenforce 0, then restarted HTTPD, and sure enough, the debug level
found the problem ... it was SELinux disabling access to the
jk-runtime-status file...
which mod_jk wanted to access at startup of httpd/mod_jk.
ewsinc wrote:
I see in the Manager/status page an error count under the AJP-8009 section
of the page.
How do I go and find out what those errors
I am running tomcat 6.0.10 on RHEL4. Apache 2.0 is the front end, via
AJP13/8009 to tomcat.
Using APR native libraries...
Everything is nominal, except that when accessing the manager/status, I see
one and only connection to Tomcat via AJP13 is the one that I am using the
view the status page. I
