[ 
http://issues.apache.org/jira/browse/DIRMINA-47?page=comments#action_66535 ]
     
Trustin Lee commented on DIRMINA-47:
------------------------------------

I checked in the fix.  It seems likt this bug only happens when you use 
Connectors not Acceptors.  Could you please try the recent JAR and reply to me?

Thanks,
Trustin



> NullPointerException in SocketIoProcessor
> -----------------------------------------
>
>          Key: DIRMINA-47
>          URL: http://issues.apache.org/jira/browse/DIRMINA-47
>      Project: Directory MINA
>         Type: Bug
>     Versions: 0.7.1
>     Reporter: Trustin Lee
>     Assignee: Trustin Lee
>      Fix For: 0.7.2

>
> Adam Hathcock wrote:
> java.lang.NullPointerException
>     at 
> org.apache.mina.io.socket.SocketIoProcessor.flush(SocketIoProcessor.java:496)
>     at 
> org.apache.mina.io.socket.SocketIoProcessor.flushSessions(SocketIoProcessor.java:402)
>     at 
> org.apache.mina.io.socket.SocketIoProcessor.access$3(SocketIoProcessor.java:377)
>     at 
> org.apache.mina.io.socket.SocketIoProcessor$Worker.run(SocketIoProcessor.java:525)
> is error I'm running into and I'm unsure of the cause.  I am closing 
> ProtocolSessions and creating new ones which may have something to do with 
> it.  I also use the DemuxingProtocolCodecFactory to manage my protocol 
> messages as well as their encoding and decoding.  
> I cannot figure out how the session's SelectionKey is becoming null.  I am 
> using a checkout of the 0.7 branch from earlier today.  
> This error occurs after I create a new connection and start using the 
> ProtocolSession.  I'm still not sure what causes it but everything appears to 
> still work if I put a try/catch for a NullPointerException in the 
> SocketIoProcessor around line 496

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Reply via email to