tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 32389] New: - ajp13 interface stops responding
Date Thu, 25 Nov 2004 12:59:31 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=32389>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=32389

           Summary: ajp13 interface stops responding
           Product: Tomcat 5
           Version: 5.5.2
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: P2
         Component: Connector:AJP
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: daniel.stanek@mius.cz


We are using tomcat-5.5.2, apache2 + mod_jk. Everything is working well but
after a while (day or two, does not directly depend on server load) tomcat stops
responding to ajp13 requests. Here is debug info from mod_jk:

[Thu Nov 25 13:33:46 2004]  [jk_uri_worker_map.c (539)]:
jk_uri_worker_map_t::map_uri_to_worker, Found a suffix match ajp13 -> *.jsp
[Thu Nov 25 13:33:46 2004]  [mod_jk.c (1689)]: Into handler r->proxyreq=0
r->handler=jakarta-servlet r->notes=136986608 worker=ajp13
[Thu Nov 25 13:33:46 2004]  [jk_worker.c (90)]: Into wc_get_worker_for_name ajp13
[Thu Nov 25 13:33:46 2004]  [jk_worker.c (94)]: wc_get_worker_for_name, done
found a worker
[Thu Nov 25 13:33:46 2004]  [mod_jk.c (472)]: agsp=80 agsn=www.autorychle.cz
hostn=www.autorychle.cz shostn=rychle.cz cbsport=0 sport=0
[Thu Nov 25 13:33:46 2004]  [jk_ajp_common.c (1741)]: Into jk_worker_t::get_endpoint
[Thu Nov 25 13:33:46 2004]  [jk_ajp_common.c (1367)]: Into jk_endpoint_t::service
[Thu Nov 25 13:33:46 2004]  [jk_ajp_common.c (257)]: Into ajp_marshal_into_msgb
[Thu Nov 25 13:33:46 2004]  [jk_ajp_common.c (425)]: ajp_marshal_into_msgb - Done
[Thu Nov 25 13:33:46 2004]  [jk_connect.c (136)]: Into jk_open_socket
[Thu Nov 25 13:33:46 2004]  [jk_connect.c (143)]: jk_open_socket, try to connect
socket = 40 to 127.0.0.1:8009
[Thu Nov 25 13:33:46 2004]  [jk_connect.c (159)]: jk_open_socket, after connect
ret = 0
[Thu Nov 25 13:33:46 2004]  [jk_connect.c (168)]: jk_open_socket, set
TCP_NODELAY to on
[Thu Nov 25 13:33:46 2004]  [jk_connect.c (185)]: jk_open_socket, return, sd = 40
[Thu Nov 25 13:33:46 2004]  [jk_ajp_common.c (701)]: In
jk_endpoint_t::ajp_connect_to_endpoint, connected sd = 40 to 127.0.0.1:8009
[Thu Nov 25 13:33:46 2004]  [jk_ajp_common.c (737)]: sending to ajp13 #547
[Thu Nov 25 13:33:46 2004]  [jk_ajp_common.c (1035)]: ajp_send_request 2:
request body to send 0 - request body to resend 0
[Thu Nov 25 13:38:28 2004]  [jk_ajp_common.c (783)]: ERROR: can't receive the
response message from tomcat, network problems or tomcat is down
(127.0.0.1:8009), err=-104

etc. Tomcat must be restarted to work again. While not responding to ajp13,
connecting directly to http interface works ok.

Here is Tomcat ajp config:

    <!-- Define an AJP 1.3 Connector on port 8009 -->
    <Connector port="8009"
               enableLookups="false" redirectPort="8443" debug="0"
               address="127.0.0.1"
               backlog="50" maxSpareThreads="75" maxThreads="220"
               soTimeout="15000"
               protocol="AJP/1.3" />


I think this is a tomcat problem. We are running binary distribution on:

bruno:/opt/jakarta/tomcat-5/conf # java -version
java version "1.5.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0-b64)
Java HotSpot(TM) Server VM (build 1.5.0-b64, mixed mode)

4-processor intel linux machine, 2.4.21

tomcat logs is full of this message:

Nov 25, 2004 1:54:39 PM org.apache.commons.modeler.Registry unregisterComponent
SEVERE: Error unregistering mbean
javax.management.RuntimeOperationsException: Object name cannot be null
        at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.isRegistered(DefaultMBeanServerInterceptor.java:545)
        at
com.sun.jmx.mbeanserver.JmxMBeanServer.isRegistered(JmxMBeanServer.java:619)
        at
org.apache.commons.modeler.Registry.unregisterComponent(Registry.java:642)
        at
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:706)
        at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:866)
        at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
        at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.IllegalArgumentException: Object name cannot be null
        ... 7 more

thanks
dan

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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


Mime
View raw message