[jboss-jira] [JBoss JIRA] Updated: (JBAS-5165) Generic ProxyFactoryHA too dependent on deployment ordering

[Brian Stansberry (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBAS-5165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry updated JBAS-5165:
-----------------------------------

    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".

> Generic ProxyFactoryHA too dependent on deployment ordering
> -----------------------------------------------------------
>
>                 Key: JBAS-5165
>                 URL: https://jira.jboss.org/jira/browse/JBAS-5165
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>    Affects Versions: JBossAS-4.2.2.GA,  JBossAS-5.0.0.Beta3
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>             Fix For: JBossAS-6.0.0.Alpha1
>
>
> org.jboss.proxy.generic.ProxyFactoryHA will not signal its HATarget to allow invocations to proceed until it receives a JMS notification that its target service has started.  But, if the target service starts before ProxyFactoryHA.create() is called, it will never get the notification.

-- 
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