[jboss-jira] [JBoss JIRA] Commented: (JBREM-782) Remove network i/o from synch block in ServerInvokerCallbackHandler.getCallbackHandler()
Ron Sigal (JIRA)
jira-events at lists.jboss.org
Mon Aug 20 02:05:01 EDT 2007
[ http://jira.jboss.com/jira/browse/JBREM-782?page=comments#action_12372888 ]
Ron Sigal commented on JBREM-782:
---------------------------------
Actually, the first attempt introduced a race condition. The solution is to move org.jboss.remoting.Client.connect() out of ServerInvokerCallbackHandler() into a new method, ServerInvokerCallbackHandler.connect().
> Remove network i/o from synch block in ServerInvokerCallbackHandler.getCallbackHandler()
> ----------------------------------------------------------------------------------------
>
> Key: JBREM-782
> URL: http://jira.jboss.com/jira/browse/JBREM-782
> Project: JBoss Remoting
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Affects Versions: 2.2.1.GA, 2.2.0.SP4, 2.4.0.Beta1 (Pinto)
> Reporter: Ron Sigal
> Assigned To: Ron Sigal
> Fix For: 2.4.0.Beta1 (Pinto), 2.2.2.GA
>
>
> org.jboss.remoting.ServerInvoker.getCallbackHandler() has a call to the org.jboss.remoting.callback.ServerInvokerCallbackHandler() constructor inside a synchronization block., ServerInvokerCallbackHandler creates an org.jboss.remoting.Client, which creates a client invoker, and, depending on the transport, the call to Client.connect() might involve network i/o.
--
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