[
https://jira.jboss.org/browse/JBREM-1257?page=com.atlassian.jira.plugin.s...
]
Ron Sigal resolved JBREM-1257.
------------------------------
Assignee: Ron Sigal
Resolution: Done
org.jboss.remoting3.remote.RemoteMessageHandler and
org.jboss.remoting3.remote.InboundRequestTask have been changed so that
RemoteMessageHandler retrieves the appropriate InboundClient and passes it to
InboundRequestTask, instead of letting InboundRequestTask retrieve the InboundClent on a
separate thread.
InboundClient should not be removed while a request is in progress
------------------------------------------------------------------
Key: JBREM-1257
URL:
https://jira.jboss.org/browse/JBREM-1257
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: r3 core: remote
Affects Versions: 3.1.0.Beta2
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 3.1.0.Beta3
An invocation of org.jboss.remoting.Client.send() will cause the execution of an
InboundRequestTask on the server, where InboundRequestTask.run() looks for the related
org.jboss.remoting3.remote.InboundClient to execute the request. An invocation of
Client.close() will result in the related InboundClient being removed from its map. Since
the InboundRequestTask is executed in a separate thread, it is possible for the removal of
the InboundClient to occur before the InboundRequestTask accesses it. The result is a
NullPointerException.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira