S Arvind wrote:
> Hi Martin & Chris,
> Thing i actually need is, if a query executed from web application then it
> shold not execute more then 22mins. If it execute more then that means query
> shold be cancelled from postgres and java should get exception on this
> event. Is it possible?
If a)
Hi Martin & Chris,
Thing i actually need is, if a query executed from web application then it
shold not execute more then 22mins. If it execute more then that means query
shold be cancelled from postgres and java should get exception on this
event. Is it possible?
Thanks,
Arvind S
*
"Many of li
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Arvind,
On 6/1/2009 3:26 PM, S Arvind wrote:
> Is there any possibility to mention max time a query can execute from DBCP
> side?
What do you want to happen after the timeout? The connection execute*
method throws an exception? That is going to be ve
DBCP specifies 60 secs before recycling the connection
http://tomcat.apache.org/tomcat-5.5-doc/jndi-datasource-examples-howto.html
hth!
Martin
"Everything comes to him who hustles while he waits" - edison
__
Verzicht und Vertraulichkeitanmerkung/Not
Is there anyother way to specify the query execution time out while
establishing connection with the help of DBCP in tomcat?
-Arvind S
On Tue, Jun 2, 2009 at 12:56 AM, S Arvind wrote:
> Is there any possibility to mention max time a query can execute from DBCP
> side? our DB is Postgres and Cont
