NullPointerException in error.log


I haven’t yet moved to 3.5.0, this is from 3.4.5. Apologies if this have been fixed in 3.5.0 already. I am not sure how serious it is, but it unnecessarily clutters the error log. I am not sure exactly what makes it happen, I guess the debug backtrace should be helpful enough. What may cause it is that the domain of the server have been changed and some users may still have items in their roster with the obsolote domain name (which is unreachable). It would be very nice if server domain change would automagically go through the rosters of all users and correct the domain names there, too (at least optionally, asked on the web interface). You could file a separate bugreport for this.

Developers, could you please indicate in this thread:

  • that you have read this,

  • that you have filed or rejected this bug report,

  • that this is fixed.

2008.04.11 14:47:18 ) Could not close socket



at org.jivesoftware.openfire.http.HttpSession$Deliverable.getPackets(HttpSession.j ava:800)

at org.jivesoftware.openfire.http.HttpSession.failDelivery(

at org.jivesoftware.openfire.http.HttpSession.closeConnection( )

at org.jivesoftware.openfire.http.HttpSession.access$200(

at org.jivesoftware.openfire.http.HttpSession$HttpVirtualConnection.closeVirtualCo nnection(

at 5)

at org.jivesoftware.openfire.http.HttpSession.close(

at org.jivesoftware.openfire.http.HttpBindServlet.sendError( 87)

at org.jivesoftware.openfire.http.HttpBindServlet.isContinuation(HttpBindServlet.j ava:166)

at org.jivesoftware.openfire.http.HttpBindServlet.doPost(

at javax.servlet.http.HttpServlet.service(

at javax.servlet.http.HttpServlet.service(

at org.mortbay.jetty.servlet.ServletHolder.handle(

at org.mortbay.jetty.servlet.ServletHandler.handle(

at org.mortbay.jetty.handler.ContextHandler.handle(

at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollect

at org.mortbay.jetty.handler.HandlerCollection.handle(

at org.mortbay.jetty.handler.HandlerWrapper.handle(

at org.mortbay.jetty.Server.handle(

at org.mortbay.jetty.HttpConnection.handleRequest(

at org.mortbay.jetty.HttpConnection.handle(


at org.mortbay.jetty.nio.SelectChannelConnector$

at org.mortbay.thread.BoundedThreadPool$

Updated to Openfire 3.5.1, and this problem seems to have been fixed.