On 21.08.2012 10:34, Veit Guna wrote:
Hi.
I'm using Atlassian Fisheye 2.7.15 (uses Jetty 6.1.26) under Ubuntu 12.04
with mod_jk 1:1.2.32-1 and Apache 2.2.22-1ubuntu1.
After I upgraded mod_jk from 1.2.31 to 1.2.32 Jetty isn't working anymore
throwing the exception below.
Any ideas why that is happening? What changed through that version?
Atlassian recommends to downgrade to 1.2.31 (of course). But that's not an
option because of missing security
updates through Ubuntu. The Jetty guys say, Atlassian should upgrade to a more
recent Jetty version - in the hope that
it is fixed there :).
Now I would like to hear your opinion/options to solve my problem :).
2012-08-02 18:03:37,644 ERROR - handle failed
java.lang.NullPointerException
at
org.mortbay.jetty.ajp.Ajp13Connection$RequestHandler.parsedRequestAttribute(Ajp13Connection.java:216)
at org.mortbay.jetty.ajp.Ajp13Parser.parseNext(Ajp13Parser.java:410)
at
org.mortbay.jetty.ajp.Ajp13Parser.parseAvailable(Ajp13Parser.java:151)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at
org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:228)
at
org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451)
I think it is this Jetty-Bugfix which is missing:
http://git.eclipse.org/c/jetty/org.eclipse.jetty.project.git/commit/jetty-ajp/src/main/java/org/eclipse/jetty/ajp/Ajp13Connection.java?id=9fb6e9b43a4803fff58f3d5d65a526b9c6078be8
i.e. you ran into this problem:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=363943
It seems there's no Jetty 6 release with this patch (the patch is not
even in the Jetty 6 head sources), you would need to use at least Jetty
7.6.0 or above.
There's no known vulnerability in mod_jk 1.2.31 but being restricted to
it without being able to do a quick update if needed doesn't sound like
a good idea. In case you do the update think about switching directly to
1.2.37.
Possible workaround (untested): If you haven't already done so,
configure an additional load balancing worker above your ajp13 worker,
even if you do not really do load balancing because only one Tomcat is
involved. It might fix the problem by setting the attribute that
triggers the NPE to some non empty value. If it works, please report back.
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
