The default transaction-timeout can be found at the "transaction" subsystem of your JBoss EAP profile (like standalone.xml) as following: (300 seconds)
It can be easily changed via JBoss-cli or console (setting 0 means disabling it)
At individual component level we can configure the timeouts as well like EJBs can be configured to use a different timeout using @
org.jboss.ejb3.annotation.TransactionTimeout or using jboss-ejb3.xml
Its already been configured to 300 Secs, (5mins) in Jboss. But the thread / resources are keep on waiting for the response.... in mean time all other transactions are in queue & servers are getting non-responsive after some time.....
The Tx-timeout does not mean the thread get's interrupted. So if i.e. a DB query hung (I saw that by create a carthesian product where the query run for hours, or maybe full-table scan (Oracle)
the java code still wait on the JDBC driver which is not interrupted.
Only the next action with the Tx-Manager will fail, so if you do a query and run an internal calculation (for hours) this will not fail until you hit the next query.
Can this the case in your issue?