[jboss-jira] [JBoss JIRA] Updated: (JBREM-654) a NullPointerException occures and is not handled in SocketServerInvoker and MultiplexServerInvoker
[ http://jira.jboss.com/jira/browse/JBREM-654?page=all ]
Claudia Richter updated JBREM-654:
----------------------------------
Attachment: TruststoreDynamicTimer.zip
I attached a sample Project, which shows the problem including a workaround I implemented
for myself. The workaround is to just catch the NullPointerException and wait for the next
reload round until a new SocketServer exists. But actually this slows down the connection
and sometimes causes timeouts (ConnectExceptions) on the Client side. So a real solution
is needed here.
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: Tom Elrod
Attachments: 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