[jboss-jira] [JBoss JIRA] (WFLY-6021) Default transaction timeout is not applied for EJB bean when set for second time

[Brian Stansberry (JIRA)]

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

Brian Stansberry commented on WFLY-6021:
----------------------------------------

It's interesting then that Ondřej reports that a reload doesn't result in a behavior change, only a restart does. (The Steps to Reproduce don't mention a reload but the main JIRA description says reload is ineffective.)

It would be great if this didn't require a reload at all. That's the goal for most any attribute.

> Default transaction timeout is not applied for EJB bean when set for second time
> --------------------------------------------------------------------------------
>
>                 Key: WFLY-6021
>                 URL: https://issues.jboss.org/browse/WFLY-6021
>             Project: WildFly
>          Issue Type: Bug
>          Components: EJB, Transactions
>            Reporter: Ondřej Chaloupka
>            Assignee: Fedor Gavrilov
>
> It seems that transaction subsystem attribute {{default-timeout}} does not have any effect for EJB if it's redefined. It means if I set the default transaction timeout in transaction subystem for second (and next) time it's not applied for EJB beans. It's used the firstly set value.
> The transaction timeout is not changed for EJB when server is reloaded. When server is restarted it refreshes all settings and EJB starts using the expected value for timeout settings.
> If the value is read from subsystem
> {{/subsystem=transactions:read-attribute(name=default-timeout)}}
> it shows correct value (that one set for second time). But EJB seems not applying it.



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