Looks like the is a TODO within the code, not sure whether it's related.
Is it possible to set the Tx timeout fo both sides with an annotation?
I don't know, this is my question, i want to change the default timeout value.
I recommenc to not set such high default timeout.
You might run into issues, i.e. if a action which is normally short takes longer all resources are blocked and you run out of DB connections or GC issues.
To change the timeout for a few methods you can use the ejb-jar.xml.
thanks for the reply
But the problem is that every remote ejb call, a transaction is created with 300 seconds timeout and if i define a timeout for some methods in the file jboss-ejb3.xml the problem persist because the ejb remote transaction will be canceled after 300 seconds, so the global transaction will be rollbacked at the commit phase (the two-phase commit strategy)
That TODO in code needs to be fixed/implemented. Please file a WFLY JIRA with the details and please point to that code in the description of that JIRA
You know about the config (standalone.xml/domain.xml)?
<recovery-environment socket-binding="txn-recovery-environment" status-socket-binding="txn-status-manager"/>
Marc, it is more that a server-to-server invocation will not respect the timeout, looks like there is a hardcoded 300ms default in this case.