[jboss-jira] [JBoss JIRA] (WFLY-8370) Changing global transaction timeout requires reload to be considered for MDB

[Ondra Chaloupka (JIRA)]

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

Ondra Chaloupka edited comment on WFLY-8370 at 3/15/17 5:35 AM:
----------------------------------------------------------------

Hi [~dmlloyd], I didn't want to assign this issue to me as you have a much clearer idea of how the fixes for WFTC should look like. But I have here a proposal that works for me
https://github.com/ochaloup/wildfly/commit/b5622bd8aaf22459d1262de8b10289c96025d8f3 (https://github.com/ochaloup/wildfly/tree/WFLY-8370-propagate-change-of-txn-timeout-to-wftc)
In general, it's just adding WFTC update at write handler in txn subsystem. If you are fine with such fix I can reassign this issue on me and process it.
Thanks for help


was (Author: ochaloup):
Hi [~dmlloyd], I didn't want to assign this issue to me as you have a much clearer idea of how the fixes for WFTC should look like. But I have here a proposal that works for me
https://github.com/ochaloup/wildfly/commit/b5622bd8aaf22459d1262de8b10289c96025d8f3 (https://github.com/ochaloup/wildfly/tree/WFLY-8370-propagate-change-of-txn-timeout-to-wftc)
In general, it's just adding WFTC update at write handler in txn subsystem. If you are fine with such fix I can reassign this issue on me and process it.
Thanks a lot for help

> Changing global transaction timeout requires reload to be considered for MDB
> ----------------------------------------------------------------------------
>
>                 Key: WFLY-8370
>                 URL: https://issues.jboss.org/browse/WFLY-8370
>             Project: WildFly
>          Issue Type: Bug
>          Components: Transactions
>    Affects Versions: 11.0.0.Alpha1
>            Reporter: Ondra Chaloupka
>            Assignee: David Lloyd
>
> When default transaction timeout is redefined during the server lifetime
> {code}
> /subsystem=transactions:write-attribute(name=default-timeout, value=60)
> {"outcome" => "success"}
> {code}
> such change is not propagated to WFTC and for example in case of MDB the default transaction timeout is being left as it was at time of container startup. The transaction timeout is considered after server is reloaded. But it's different behavior than it was and in general for transaction timeout redefinition should not be needed container reload.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)