[jboss-jira] [JBoss JIRA] (WFLY-5556) Configure remote tx timeout via system property

[RH Bugzilla Integration (JIRA)]

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

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

Jan Martiska <jmartisk at redhat.com> changed the Status of [bug 1265300|https://bugzilla.redhat.com/show_bug.cgi?id=1265300] from ON_QA to VERIFIED

> Configure remote tx timeout via system property
> -----------------------------------------------
>
>                 Key: WFLY-5556
>                 URL: https://issues.jboss.org/browse/WFLY-5556
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: EJB
>            Reporter: Panagiotis Sotiropoulos
>            Assignee: Panagiotis Sotiropoulos
>             Fix For: 10.0.0.CR4
>
>
> Description of problem:
> The hardcoded 5 minute timeout period was replace with Integer.MAX_VALUE for the timeout period of "remote" distributed transaction branches.
> - https://issues.jboss.org/browse/WFLY-2789
> - https://bugzilla.redhat.com/show_bug.cgi?id=1056585#c1
> An "infinite" timeout is a problem as this value is also passed to the database to control statement execution. This means that database statements may run uncontrolled in most cases. Too, in one case we have seen that the database driver or the database is mishandling the value and aborting almost immediately (e.g. after only 2 or 3 seconds).
> Version-Release number of selected component (if applicable):
> How reproducible:
> Consistently
> Steps to Reproduce:
> 1. Start a transaction in server "one"
> 2. Using JTA/EJB remoting, propagate that transaction to a remote server
> 3. The timeout for the transaction on the remote can be seen to be Integer.MAX_VALUE
> Actual results:
> Either an "infinite" timeout period for database statement execution or else an immediate abort
> Expected results:
> A "reasonable" smaller value must be used.



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