[jboss-jira] [JBoss JIRA] Closed: (JBAS-4614) UnifiedInvokerHAProxy does not implement InvokerProxyHA

Tue Sep 11 18:08:12 EDT 2007

     [ http://jira.jboss.com/jira/browse/JBAS-4614?page=all ]

Brian Stansberry closed JBAS-4614.
----------------------------------

    Resolution: Done

> UnifiedInvokerHAProxy does not implement InvokerProxyHA
> -------------------------------------------------------
>
>                 Key: JBAS-4614
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4614
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>    Affects Versions: JBossAS-4.0.5.GA, JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2, JBossAS-4.2.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
>
>
> UnifiedInvokerHAProxy does not implement InvokerProxyHA.  Because of this, ProxyFactoryHA will not update a unified invoker proxy's target list when it gets a notification of a cluster topology change.  Effect is a client downloading the proxy will always get the set of targets available when the proxy was created.
> Usually the downloaded proxy will also have at least one valid target (the one for the node that created the proxy.) As soon as the client makes an invocation, the server will detect they have a stale view and piggyback the current targets with the response. So, this bug is not very likely to cause an invocation failure, but it does reduce the robustness of the proxy.

-- 
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira