[
http://jira.jboss.com/jira/browse/JBREM-654?page=all ]
Claudia Richter updated JBREM-654:
----------------------------------
Attachment: SocketServerInvoker.java
I guess I found the solution. The NullPointerException was thrown when the
ServerSocketRefresh Thread did set socketServer to null, but the closing of socketServer
was not finished. So the main Thread still ran the socketServer.accept() method. a simple
flag which is set, when the accept method throws a SocketException solved the problem. I
did attach the SocketServerInvoker class, in which the flag is used.
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, 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