[jboss-jira] [JBoss JIRA] Closed: (JBAS-7014) JChannelFactory addSingletonName handling broken
Brian Stansberry (JIRA)
jira-events at lists.jboss.org
Tue Nov 17 16:12:46 EST 2009
[ https://jira.jboss.org/jira/browse/JBAS-7014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Stansberry closed JBAS-7014.
----------------------------------
Fix Version/s: JBossAS-6.0.0.M2
(was: JBossAS-6.0.0.M3)
Resolution: Done
> JChannelFactory addSingletonName handling broken
> ------------------------------------------------
>
> Key: JBAS-7014
> URL: https://jira.jboss.org/jira/browse/JBAS-7014
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Clustering
> Affects Versions: JBossAS-5.1.0.CR1, JBossAS-5.1.0.GA
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Minor
> Fix For: JBossAS-6.0.0.M1, JBossAS-6.0.0.M2
>
>
> The expected path for the AS JChannelFactory's addSingletonName logic is broken -- it thinks it is mutating the passed in config but it isn't.
> Luckily this is minor because there's separate logic that executes when JGroups throws an UnsupportedOperationException -- said logic works correctly and JGroups always throws the exception. But if a later release of JGroups fixed the UOE, this bug would be exposed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list