I'm not having a problem setting the timeout from there. Not sure what problem you could be hitting.
There are other places this value can be set and I'm not sure which one 'wins' if it's set multiple places. Do you have a jboss-ejb3.xml or annotation that could be overwriting the default timeout in the standalone-full-ha.xml?
It is possible to override the default with annotations or descriptor in your application.
BTW which version do you use? I did not see that problem in EAP6
I appreciate the quick response.
We are using Jboss EAP 6.1 .
This is weird because if we try 3000 then again issue is reproducible. But if i put timeout value in standalone as -1 or 0 then transaction does not timeout.
But now i know that i can override it only in 3 ways -
1. In standalone transaction subsystem
2. TransactionTimeout Attribute at method/class level
3. jboss-ejb3.xml file- Is it still valid in Jboss EAP 6.1 ?
Yes the override places are correct.
But such huge default timeout seems odd to me for some reasons.
What if you set 60 instead of 300?
Can you try checking and/or changing the value via the command line interface?
[standalone@localhost:9999 /] /subsystem=transactions/:write-attribute(name=default-timeout,value=3000)
and then read it back to check that it worked:
[standalone@localhost:9999 /] /subsystem=transactions/:read-attribute(name=default-timeout)
and then reboot the server
I'm curious to see what jboss thinks this value is since it seems to be stuck on 60 seconds.