[jboss-jira] [JBoss JIRA] Updated: (JBAS-3355) DetachedHANamingService does not register its ObjectName with Registry
Brian Stansberry (JIRA)
jira-events at lists.jboss.org
Mon Dec 15 17:31:54 EST 2008
[ https://jira.jboss.org/jira/browse/JBAS-3355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Stansberry updated JBAS-3355:
-----------------------------------
Fix Version/s: JBossAS-6.0.0.Alpha1
(was: JBossAS-5.0.1.CR1)
Moving issues that won't happen for next AS release after 5.0.0 (whether called 5.0.1 or 5.1.0) to AS 6. It might get pulled back to a 5.x release; just don't want it on the 5.0.1/5.10 roadmap which to me at this point both might mean "the one after 5.0.0.GA".
> DetachedHANamingService does not register its ObjectName with Registry
> ----------------------------------------------------------------------
>
> Key: JBAS-3355
> URL: https://jira.jboss.org/jira/browse/JBAS-3355
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Clustering, Naming
> Affects Versions: JBossAS-4.0.4.GA
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Minor
> Fix For: JBossAS-6.0.0.Alpha1
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> DetachedHANamingService does not register its ObjectName with Registry. Because of this, if it is used with ProxyFactoryHA and JRMPInvokerHA, calls to it will fail in JRMPInvokerHA.invoke due to a failure lookup the ObjectName in the registry.
> The purpose of having DetachedHANamingService as a distinct base class from HANamingService is to allow use with the detached invokers, so not having this work kind of defeats the point.
--
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