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

[RH Bugzilla Integration (JIRA)]

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

RH Bugzilla Integration commented on WFLY-5348:
-----------------------------------------------

Panagiotis Sotiropoulos <psotirop at redhat.com> changed the Status of [bug 1265300|https://bugzilla.redhat.com/show_bug.cgi?id=1265300] from NEW to ASSIGNED

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