https://issues.apache.org/bugzilla/show_bug.cgi?id=49770
Summary: After graceful restart using mod_proxy_ajp, NPE in
org.apache.coyote.ajp.AjpMessage
Product: Tomcat 5
Version: 5.5.30
Platform: PC
OS/Version: Linux
Status: NEW
Severity: major
Priority: P2
Component: Connector:AJP
AssignedTo: dev@tomcat.apache.org
ReportedBy: mar...@mbs3.org
After a graceful restart of our RHEL 5.5's Apache 2.2
(httpd-2.2.3-43.el5.x86_64), all four of our webservers complained that:
[Tue Aug 17 08:48:54 2010] [notice] Graceful restart requested, doing restart
[Tue Aug 17 09:28:41 2010] [error] (111)Connection refused: proxy: AJP: attempt
to connect to 128.227.74.27:8000 (sakaiapp-prod06.osg.ufl.edu) failed
[Tue Aug 17 09:28:41 2010] [error] ap_proxy_connect_backend disabling worker
for (sakaiapp-prod06.osg.ufl.edu)
[Tue Aug 17 09:28:41 2010] [error] proxy: AJP: failed to make connection to
backend: sakaiapp-prod06.osg.ufl.edu
[Tue Aug 17 09:28:41 2010] [error] proxy: BALANCER:
(balancer://elearning2.courses.ufl.edu). All workers are in error state for
route (sakaiapp-prod05.osg.ufl.edu)
[Tue Aug 17 09:32:00 2010] [error] (111)Connection refused: proxy: AJP: attempt
to connect to 128.227.74.13:8000 (sakaiapp-prod04.osg.ufl.edu) failed
[Tue Aug 17 09:32:00 2010] [error] ap_proxy_connect_backend disabling worker
for (sakaiapp-prod04.osg.ufl.edu)
[Tue Aug 17 09:32:00 2010] [error] proxy: AJP: failed to make connection to
backend: sakaiapp-prod04.osg.ufl.edu
[Tue Aug 17 09:32:00 2010] [error] proxy: BALANCER:
(balancer://elearning2.courses.ufl.edu). All workers are in error state for
route (sakaiapp-prod03.osg.ufl.edu)
In the Tomcat 5.5.30 logs, we saw hundreds of:
2010-08-17 09:00:34.601 [ERROR] org.apache.coyote.ajp.AjpMessage:239 - Cannot
append null value
java.lang.NullPointerException
at org.apache.coyote.ajp.AjpMessage.appendString(AjpMessage.java:239)
at org.apache.coyote.ajp.AjpMessage.appendBytes(AjpMessage.java:175)
at
org.apache.coyote.ajp.AjpAprProcessor.prepareResponse(AjpAprProcessor.java:1005)
at
org.apache.coyote.ajp.AjpAprProcessor.action(AjpAprProcessor.java:510)
at org.apache.coyote.Response.action(Response.java:183)
at org.apache.coyote.Response.sendHeaders(Response.java:379)
at
org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:313)
at
org.apache.catalina.connector.OutputBuffer.close(OutputBuffer.java:280)
at
org.apache.catalina.connector.Response.finishResponse(Response.java:484)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:177)
at
org.apache.coyote.ajp.AjpAprProcessor.process(AjpAprProcessor.java:444)
at
org.apache.coyote.ajp.AjpAprProtocol$AjpConnectionHandler.process(AjpAprProtocol.java:472)
at
org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1293)
at java.lang.Thread.run(Thread.java:619)
All I can figure is that this a bug in the AJP connector on the Tomcat side,
though doing a 'real' (i.e. not graceful) restart of Apache httpd fixed the
issue.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
