* The forums are not here so you can avoid reading the documentation and release notes
* Questions about EJB or jdbc persistence in general belong in the persistence forum.
Here is an overview of the history for somebody who finds this thread in future:
JDBC has a feature that lets you limit how long a query will run.
In JBoss-3.2.x a feature was added that lets you automatically set this to
the time remaining in the JTA transaction (assuming you have one).
However, the person that added this, did not apply it to the 4.0.x codebase.
This was corrected in 4.0.3
with other possible timeout configurations also added.
1) Your database has an internal configuration for this (e.g. a resource constraint)
2) Your jdbc driver has a connection property to set it for the connection as a whole
3) Your jdbc framework (CMP/EJB3/Hibernate/other) supports it (e.g. org.hibernate.timeout)
4) You set it yourself using the jdbc api
It isn't going to work on 4.0.0 through 4.0.2