[jboss-jira] [JBoss JIRA] Closed: (JBREM-654) a NullPointerException occures and is not handled in SocketServerInvoker and MultiplexServerInvoker
Ron Sigal (JIRA)
jira-events at lists.jboss.org
Mon Feb 26 02:28:46 EST 2007
[ http://jira.jboss.com/jira/browse/JBREM-654?page=all ]
Ron Sigal closed JBREM-654.
---------------------------
Resolution: Done
Access to the ServerSocket has been synchronized in SocketServerInvoker.
Thanks to Claudia Richter for alerting us to this problem.
> a NullPointerException occures and is not handled in SocketServerInvoker and MultiplexServerInvoker
> ---------------------------------------------------------------------------------------------------
>
> Key: JBREM-654
> URL: http://jira.jboss.com/jira/browse/JBREM-654
> Project: JBoss Remoting
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: transport, transport-multiplex, transporter
> Affects Versions: 2.2.0.Alpha4, 2.2.0.Alpha3 (Bluto), 2.0.0.GA (Boon), 2.0.0.CR1 (Boon)
> Reporter: Claudia Richter
> Assigned To: Ron Sigal
> Fix For: 2.2.0.Beta1 (Bluto)
>
> Attachments: SocketServerInvoker.java, SocketServerInvoker.java, TruststoreDynamicTimer.zip
>
>
> when trying to dynamically load keystores several times, it happens that the SocketServer is set to null and a NullPointerException is thrown. MultiplexServerInvoker and SocketServerInvoker are both not able to handle this Exception. Actually no NullPointerException should be thrown, but it happens. This Exception causes the Server to fail.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list