[ http://jira.jboss.com/jira/browse/JBREM-25?page=history ]
Tom Elrod closed JBREM-25:
---------------------------
Resolution: Done
Updated the code in both 3.2 branch (so should become part of 3.2.7 release)
and HEAD (which will be backported to 4.0 branch shortly).
public static void destroyClientInvoker(InvokerLocator locator)
{
ClientInvoker invoker = null;
synchronized(clientLock)
{
invoker = (ClientInvoker) clientLocators.remove(locator);
}
if(invoker != null)
{
if(log.isDebugEnabled())
{
log.debug("destroying client for locator: " + locator + ",
invoker:" + invoker + ", remaining list:" + clientLocators);
}
invoker.disconnect();
invoker = null;
}
}
> Deadlock in InvokerRegistry
> ---------------------------
>
> Key: JBREM-25
> URL: http://jira.jboss.com/jira/browse/JBREM-25
> Project: JBoss Remoting
> Type: Bug
> Components: general
> Versions: 1.0.1 alpha
> Reporter: Tom Elrod
> Assignee: Tom Elrod
> Fix For: 1.0.1 beta
> Attachments: InvokerRegistry.java
>
>
> From Jeff Haynie:
> We found a pretty nasty deadlock at a production site this past week in
> remoting. I'm attaching the file that changed, you should be able to diff
> it. It was a synchronized change.
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
