[jboss-jira] [JBoss JIRA] Resolved: (JBAS-5850) Tx sticky lbp issue with shutdown nodes

[Galder Zamarreno (JIRA)]

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

Galder Zamarreno resolved JBAS-5850.
------------------------------------

    Resolution: Done


> Tx sticky lbp issue with shutdown nodes
> ---------------------------------------
>
>                 Key: JBAS-5850
>                 URL: https://jira.jboss.org/jira/browse/JBAS-5850
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>    Affects Versions: JBossAS-5.0.0.CR1, JBossAS-4.2.3.GA
>            Reporter: Galder Zamarreno
>            Assignee: Galder Zamarreno
>             Fix For: JBossAS-5.0.0.CR2, JBossAS-4.2.4.GA
>
>
> When using transaction sticky load balance policies, before making an 
> invocation, we check whether there's a sticky target in the tx failover 
> authorisation map and if there is, we add it to the transient payload.
> The sticky lbps then check that sticky target and if available in the cluster, 
> they use it. However, if there's a sticky target was set but it's not available,
> we chose a new target when indeed we should fail cos the transaction 
> already reached the server (if it hadn't reached a server yet, there're 
> wouldn't  be a sticky target at all).
> I can see this causing issues when shutting down a node that was being 
> used in a transaction. The problem is that the node shutdown will be chosen 
> as sticky target but as it's not available, so it choses a a brand new one. It 
> should have instead failed.

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