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.