NullPointerException While resource conflict in 3.5.1

I am getting NullPointer Exception When I Use same resource. Use case as follows:

From user A logs in to messenger in HTTP-Bind mode. The same user A logs in to messenger in TCP mode using same resouce. In this case this NullPointerException occured.

Is there any issue to related to this in JIRA. I not found this bug in Openfire3.6.0a. Is this resolved.

Anybody who knows about this. Reply me back

2008.09.20 12:24:11 [org.jivesoftware.openfire.net.VirtualConnection.close(VirtualConnection.java:1 60)] Could not close socket
org.jivesoftware.openfire.http.HttpSession$HttpVirtualConnection@1140db
java.lang.NullPointerException
at org.jivesoftware.openfire.http.HttpSession$Deliverable.getPackets(HttpSession.j ava:809)
at org.jivesoftware.openfire.http.HttpSession.failDelivery(HttpSession.java:682)
at org.jivesoftware.openfire.http.HttpSession.closeConnection(HttpSession.java:671 )
at org.jivesoftware.openfire.http.HttpSession.access$200(HttpSession.java:52)
at org.jivesoftware.openfire.http.HttpSession$HttpVirtualConnection.closeVirtualCo nnection(HttpSession.java:740)
at org.jivesoftware.openfire.net.VirtualConnection.close(VirtualConnection.java:15 6)
at org.jivesoftware.openfire.http.HttpSession.close(HttpSession.java:161)
at org.jivesoftware.openfire.handler.IQBindHandler.handleIQ(IQBindHandler.java:118 )
at org.jivesoftware.openfire.handler.IQHandler.process(IQHandler.java:49)
at org.jivesoftware.openfire.IQRouter.handle(IQRouter.java:349)
at org.jivesoftware.openfire.IQRouter.route(IQRouter.java:101)
at org.jivesoftware.openfire.spi.PacketRouterImpl.route(PacketRouterImpl.java:68)
at org.jivesoftware.openfire.net.StanzaHandler.processIQ(StanzaHandler.java:299)
at org.jivesoftware.openfire.net.ClientStanzaHandler.processIQ(ClientStanzaHandler .java:79)
at org.jivesoftware.openfire.net.StanzaHandler.process(StanzaHandler.java:264)
at org.jivesoftware.openfire.net.StanzaHandler.process(StanzaHandler.java:163)
at org.jivesoftware.openfire.nio.ConnectionHandler.messageReceived(ConnectionHandl er.java:133)
at org.apache.mina.common.support.AbstractIoFilterChain$TailFilter.messageReceived (AbstractIoFilterChain.java:570)
at org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(Ab stractIoFilterChain.java:299)
at org.apache.mina.common.support.AbstractIoFilterChain.access$1100(AbstractIoFilt erChain.java:53)
at org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceive d(AbstractIoFilterChain.java:648)
at org.apache.mina.common.IoFilterAdapter.messageReceived(IoFilterAdapter.java:80)
at org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(Ab stractIoFilterChain.java:299)
at org.apache.mina.common.support.AbstractIoFilterChain.access$1100(AbstractIoFilt erChain.java:53)
at org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceive d(AbstractIoFilterChain.java:648)
at org.apache.mina.filter.codec.support.SimpleProtocolDecoderOutput.flush(SimplePr otocolDecoderOutput.java:58)
at org.apache.mina.filter.codec.ProtocolCodecFilter.messageReceived(ProtocolCodecF ilter.java:180)
at org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(Ab stractIoFilterChain.java:299)
at org.apache.mina.common.support.AbstractIoFilterChain.access$1100(AbstractIoFilt erChain.java:53)
at org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceive d(AbstractIoFilterChain.java:648)
at org.apache.mina.filter.executor.ExecutorFilter.processEvent(ExecutorFilter.java :239)
at org.apache.mina.filter.executor.ExecutorFilter$ProcessEventsRunnable.run(Execut orFilter.java:283)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java: 885)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnable.java:51)
at java.lang.Thread.run(Thread.java:619)

Hi,

Thanks for reporting your issue. I attempted to reproduce this on 3.6.0a and was not able to. There were lots of changes in 3.6.0 with http-bind, so I bet this was fixed.

daryl