TransactionManagerService timeout setting change?

[didickman]

We have an enterprise application that times out due to a long running JDBC query (the query is processing a very large quantity of data). Changing the "TransactionTimeout" setting in jboss-service.xml from 300 to 900 fixes this for us. Does it make sense to make the default in JBoss something like 900?

Would there be any downside to shipping JBoss with this larger value by default?

Thanks.

[starksm64]

As of jboss-3.2.4 you can set the timeout at the ejb method level. See the jta notes here:
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=48895

[didickman]

This is pretty neat and fortunately we're using 3.2.5 so I'll definitely give this a try.

But back to the original question, is there any reason not to increase the default value? What if we have many methods that would otherwise need transaction-timeout attributes to be set?

[starksm64]

The downside is excessively long time to detection of deadlocks for those scenarios jboss itself cannot detect. This may or may not be important as it depends on your application behavior.