3.0.4 -> 3.0.5: jetty changes?

[tek1]

i just tried upgrading from jboss 3.0.4 to 3.0.5, and an application that worked fine in 3.0.4 is throwing a NullPointerException in 3.0.5. anyone familiar with jetty might know what would have caused the below exception?

i'm using jdk1.4.1_01 and jboss-3.0.5_jdk141.zip. not quite sure, but it appears to be having a problem with the filter not being able to pass the call/request to the servlet...

thank you.


00:49:21,069 WARN [jbossweb] WARNING: Exception for /myprj/test
java.lang.NullPointerException
at java.io.Writer.write(Writer.java:126)
at myprj.j2ee.servlet.filter.ClientSessionIdHandlingFilter.doFilter(
Unknown Source)
at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApp
licationHandler.java:320)
at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicati
onHandler.java:272)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:5
53)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1656)
at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplication
Context.java:549)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1606)
at org.mortbay.http.HttpServer.service(HttpServer.java:862)
at org.jboss.jetty.Jetty.service(Jetty.java:497)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:752)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:916)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:769)
at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:
202)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:289)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:455)

[jules]

look at the stacktrace.

the NPE is in your code : myprj.j2ee.servlet.filter.ClientSessionIdHandlingFilter.doFilter which is compiled without debugging - so you don't have a line number....

Look at your code before posting here. If you find Jetty behaves in a way that you believe contravenes the spec, or is different from other implementations, then give me a concise description of the difference and I will look into it.

Jules

[tek1]

thank you for your reply.

i will look further into the problem, but the problem does not exist in jboss3.0.4 nor jboss3.2.0rc1, which led me to suspect that there might have been a change in the way jetty handles filter processing between the version.

thank you.

[jules]

It may well be so - but your first port of call should be the line that the exception is thrown from. If you figure out why you are getting the NPE we will have a much better chance of figuring out what happened.

Cheers,

Jules