Hi,
If you are using a connection pooling, then may be the pool manager is
closing the connection if connection has been idle for a long time (if
some code is there that takes long) after it has been opened. If the
connections remains open for long time, pool manager may consider of it
as abandoned and can take back in the pool.
If you are using DBCP connection pooling, try changing
'removeAbandonedTimeout' parameter to a bigger value.
regards,
Pushker
nalini wrote:
> I am facing the following problem.
>
> Our application sends a block of queries to postgres in a begin end block. If one of the queries take a long time to
finishthe whole transaction is assumed to be committed by the application even though the query is still running . This
resultsin failure of all subsequent transactions.
>
> Although the application is programmed to catch all exceptions , it somehow is not able to figure out that the
transactionis still not complete.
>
> I am using postgres 8.3
>
> with regards
>
> Nalini
>
>
The information contained in this electronic message and any attachments to this message are intended for the exclusive
useof the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended
recipient,you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy
theoriginal message all copies of this message and any attachments.
WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for
thepresence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
Please do not print this email unless it is absolutely necessary.