Hi,
We maintain a pool it is just a collection, where we maintain a list
of connections.
Regards
prasad
Message
From: Robert DiFalco [mailto:rdifalco (AT) tripwire (DOT) com]
Sent: Wednesday, August 23, 2006 11:41 PM
To: Prasad Ramisetti (WT01 - Broadband Networks); mysql (AT) lists (DOT) mysql.com
Subject: RE: Problem with INNDB transactions
What connection pool code are you using? My guess is that the problem is
in your code somewhere. Either transactions are not being closed (i.e.
because of a connection pool flaw maybe?) or you have two threads trying
to update the same row at the same time (in which case this would be
expected behavior).
R.
Message
From: prasad.ramisetti (AT) wipro (DOT) com [mailto:prasad.ramisetti (AT) wipro (DOT) com]
Sent: Wednesday, August 23, 2006 9:31 AM
To: mysql (AT) lists (DOT) mysql.com
Subject: Problem with INNDB transactions
Hi,
I am facing a strange problem with INNDB. My application communicates
with mysql server using JDBC. I am using mysql 5.1 version.
Even after issuing connection.commit() / connection.rollback() commands,
still on the sql side the transactions are not getting closed properly.
In our application we never try to acquire locks on the same row from
different threads. A request is sent only when the previous transaction
is closed by issuing commit or rollback. But still the following error
is seen :
"Lock wait timeout exceeded; try restarting transaction".
The transaction isolation level used is "READ-CMMITTED". We maintain a
database connection pool and try to reuse the connections from the pool
instead of trying to close and create the connections everytime. In our
application there is a continuous database updates happening at a very
high rate.
Could you please suggest what could be going wrong.
Thanks
Prasad
The information contained in this electronic message and any attachments
to this message are intended for the exclusive use of 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 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 the presence of viruses.
The company accepts no liability for any damage caused by any virus
transmitted by this email.
www.wipro.com
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of 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 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 the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
www.wipro.com