On 19 May (11:35), Aaron Knauf wrote:

> Lookup the UserTransaction and call setTransactionTimeout() on it before calling 
> begin().  In the case of a non-JTA environment, there is no way to set the 
> transaction timeout as transactions do not normally timeout, so it becomes 
> irrelevant.  Of course, it would be possible, (even easy,) if there were a 
> requirement, to implement a mechanism by which standard JDBC transactions were 
> rolled back after a timeout, but I do not see a need for it right now.

I think I didn't understand you fully, because I thought that this was
exactly what you wanted and I don't see a way to implement it. The JTA
timeout can certainly be set, but then again, you can already define
that in our application server configuration.

-- 
Christian Bauer
[EMAIL PROTECTED]
http://hibernate.org/


-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
_______________________________________________
hibernate-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/hibernate-devel

Reply via email to