[jboss-jira] [JBoss JIRA] Reopened: (JBAS-8582) Under certain circumstances a wrong locator can be removed from UnifiedInvokerHAProxy
Jason Greene (JIRA)
jira-events at lists.jboss.org
Thu Apr 21 14:27:11 EDT 2011
[ https://issues.jboss.org/browse/JBAS-8582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Greene reopened JBAS-8582:
--------------------------------
Due to feedback from the community, I have split the AS7 and AS6 projects and reopened all unscheduled AS6 issues that are a year or less old. This will make it easier community members to find and work on them.
Future releases beyond 6.1 can be done provided a community member steps up to coordinate them.
> Under certain circumstances a wrong locator can be removed from UnifiedInvokerHAProxy
> --------------------------------------------------------------------------------------
>
> Key: JBAS-8582
> URL: https://issues.jboss.org/browse/JBAS-8582
> Project: Legacy JBoss Application Server 6
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: JBossAS-5.1.0.GA
> Environment: JBoss EJB 2.1
> Reporter: Tom Ross
> Assignee: Tom Ross
> Fix For: No Release
>
>
> Thee is a small window of opportunity that under failure conditions, the locator removed could be the wrong one.
> Under error condition UnifiedInvokerHAProxy class calls removeDeadTarget(getLocator()) method. Problem is that the getLocator() call might return a locator not associated with current client.
> This should be changed to removeDeadTarget(client.getInvoker().getLocator()). This way we can be sure that correct locator is aways used.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list