[jboss-jira] [JBoss JIRA] Closed: (JBAS-4802) FirstAvailable target should not be transient

[Brian Stansberry (JIRA)]

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

Brian Stansberry closed JBAS-4802.
----------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
       Resolution: Done

In the new org.jboss.ha.client.loadbalance.FirstAvailable, this field is no longer transient.  It is still transient in the legacy org.jboss.ha.framework.interfaces.FirstAvailable class, as I did not want to break serialization compatibility.

> FirstAvailable target should not be transient
> ---------------------------------------------
>
>                 Key: JBAS-4802
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4802
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>            Priority: Minor
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> If a bean proxy that already has a target established gets serialized (e.g. passed through a remote call), the sticky target is lost on the other end.  This can lead to invocations against the same target bean on multiple servers.
> I don't see any reason for FirstAvailable.electedTarget to be transient.
> Problem here is changing this changes the serialized form of the class, breaking interoperability.  Class also does not implement Externalizable.

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