[jboss-jira] [JBoss JIRA] Commented: (JBAS-6056) UserTransaction cannot be deployed as clustered proxy and sticky transactions randomly work

[Isaac Rooskov (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBAS-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12442746#action_12442746 ] 

Isaac Rooskov commented on JBAS-6056:
-------------------------------------

Thank-you for the excellent svn commit messages, this has assisted me in writing the Release Notes for the EAP greatly. 

> UserTransaction cannot be deployed as clustered proxy and sticky transactions randomly work
> -------------------------------------------------------------------------------------------
>
>                 Key: JBAS-6056
>                 URL: https://jira.jboss.org/jira/browse/JBAS-6056
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering, Transaction Manager (JBossTM)
>    Affects Versions: JBossAS-4.2.3.GA, JBossAS-5.0.0.CR2
>            Reporter: Galder Zamarreno
>            Assignee: Galder Zamarreno
>             Fix For: JBossAS-5.0.0.GA
>
>
> When using sticky transactions calling clustered EJBs, user transaction currently uses a non-clustered
> proxy which means that UserTransaction (UT) calls will always land in the same node. This has a bad side effect in the case
> of dealing with clustered transaction sticky EJBs.
> If the UT and EJB calls landed on the same node, everything works fine: no matter how many EJB calls are
> done within a UT, they're all part of the same UT.
> If the UT lands on one node but all the sticky EJB calls land on a different node, each EJB invocation is effectively
> treated as a separate transaction because the tpc (transaction propagation context) does not exist in that node.
> UserTransaction needs to be able to be deployed with a clustered proxy that supports sticky transactions in the sense that:
> - Wherever ut.begin() lands, the EJB invocations within it and other ut operations (ut.commit(),ut.rollback()...etc) must 
> land in the same node.
> - Consecutive ut.begin() calls are free to land on different nodes, based on what the lbp is. For example, in the case
> of TransactionStickyRoundRobin, the next ut.begin() call will land on the next node in the view of the cluster.

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