When using the latest version of mod_jk
(1.2.32) to connect to a jetty service 6.1 or later we receive a NullPointerException
in the RequestHandler class.
java.lang.NullPointerException
at org.eclipse.jetty.ajp.Ajp13Connection$RequestHandler.parsedRequestAttribute(Ajp13Connection.java:215)
at org.eclipse.jetty.ajp.Ajp13Parser.parseNext(Ajp13Parser.java:406)
at org.eclipse.jetty.ajp.Ajp13Parser.parseAvailable(Ajp13Parser.java:150)
at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:411)
at org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector.java:241)
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:529)
at java.lang.Thread.run(Thread.java:722)
This is happening because in the newest
mod_jk a request attribute, 'JK_LB_ACTIVATION', was added. When the
Apache server is not configured to use the mod_jk load balancing, the value
of JK_LB_ACTIVATION comes in as a null.
We have tested various version of Jetty
from 5.1.x through 8.0.0.M3 and the problem consistently occurs whenever
the latest mod_jk is used.
Is anyone else seeing this issue? Due
to company driven security patches, we are required to use the latest mod_jk
connector. So any help here would be greatly appreciated.
Thanks!
Mike
