[jboss-jira] [JBoss JIRA] (WFLY-5348) Propagate transaction timeout value for distributed transaction when using JTA and EJB remoting

[David Lloyd (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-5348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13108945#comment-13108945 ] 

David Lloyd commented on WFLY-5348:
-----------------------------------

The protocol actually doesn't have a space for this value.  It will have to wait until at least 11.x where the EJB and transaction wire protocols can be updated as needed.  There will still be no way to propogate this timeout information between a newer node and an older one though.

> Propagate transaction timeout value for distributed transaction when using JTA and EJB remoting
> -----------------------------------------------------------------------------------------------
>
>                 Key: WFLY-5348
>                 URL: https://issues.jboss.org/browse/WFLY-5348
>             Project: WildFly
>          Issue Type: Bug
>          Components: EJB
>    Affects Versions: 10.0.0.Beta2
>            Reporter: Stephen Fikes
>              Labels: ejb3, jta, transactions
>
> When a transaction begins in "server 1" and an EJB remoting request is made to "server 2" the timeout value for the transaction branch in "server 2" is initially set to {{Integer.MAX_VALUE}} which means {{set-tx-query-timeout}} does not work properly on datasources enlisted in the distributed branch of the transaction in server 2. This essentially requests that statement execution not be timed out at all (though in some cases the large value seems to result in abnormally fast timeout after a couple of seconds).



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)