cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hunsberger, Peter" <Peter.Hunsber...@STJUDE.ORG>
Subject RE: Session Timeout listener (was: RE: [RT] The API for the request object)
Date Tue, 06 Jul 2004 18:43:05 GMT
Colin Paul Adams <colin@colina.demon.co.uk> writes:

> 
> >>>>> "Peter" == Hunsberger, Peter 
> <Peter.Hunsberger@STJUDE.ORG> writes:
> 
>     Peter> Colin Paul Adams <colin@colina.demon.co.uk> writes:
>     Peter> <snip>flow listener discussion,/snip>
>     >>  I've just read this thread, because I have been trying to work
>     >> out how to implement pessimistic locking within cocoon.  A
>     >> problem is how to close a database transaction if the user
>     >> simply walks away from the computer for a few hours, in the
>     >> middle of a transaction. Session timeout will close the
>     >> session, but a session listener is needed to then go and
>     >> rollback the database transaction (or any other such resources
>     >> held).
> 
>     Peter> Maybe I'm missing something, but why aren't you setting
>     Peter> your database transaction timeout limit to something just a
>     Peter> bit larger than the session timeout?
> 
> Well, I guess this is fine for a database server dedicated to 
> the application (which is OK for my usage). But it's not a 
> general solution to resources being held by sessions. I 
> thought I'd raise the issue while listeners were being discussed.

I believe you should be able define the timeout at the DB (JDBC/ODBC?)
connection pool level when you define the connection for the
application, not?



Mime
View raw message