no issues with the upgrade.
When rolling out to production we started getting lock timeouts that
would bring the system down under heavy load.
We did not recreate the JNDI datasource or replace any database drivers
on the WebSphere machines or make any configuration changes within DB2
(other
no issues with the upgrade.
When rolling out to production we started getting lock timeouts that would
bring the system down under heavy load.
We did not recreate the JNDI datasource or replace any database drivers on
the WebSphere machines or make any configuration changes within DB2 (other
than
2.0.9 to the latest release 2.3.1.
The dev and test environment showed no issues with the upgrade.
When rolling out to production we started getting lock timeouts that would
bring the system down under heavy load.
We did not recreate the JNDI datasource or replace any database drivers
that locks
are not because of bugs in my application, and if looking into ibatis logs
revealed nothing...
Not quite helpful, sry
--
View this message in context:
http://www.nabble.com/Deadlock-found-when-trying-to-get-lock-%28MySQL-5.0-with-innodb%29-tf2792164.html#a9103064
Sent from
.
Thanks!
--
View this message in context:
http://www.nabble.com/Deadlock-found-when-trying-to-get-lock--try-restarting-transaction-tf3157415.html#a8756469
Sent from the iBATIS - User - Java mailing list archive at Nabble.com.
--
View this message in context:
http://www.nabble.com/Deadlock
the cause. If anyone could point me in the right direction of what
I
should be looking I would appreciate it - if more information is
needed,
please let me know.
Thanks!
--
View this message in context:
http://www.nabble.com/Deadlock-found-when-trying-to-get-lock--try-restarting-transaction
clinton, thanks I think that might be the case... I went ahead and added some
exception trapping to handle the deadlocks and the more recent occurences of
Lock Timeout messages such that the code has a max # of retries and sleeps
in between those. So far that seems to be working.
Any idea
!
--
View this message in context:
http://www.nabble.com/Deadlock-found-when-trying-to-get-lock--try-restarting-transaction-tf3157415.html#a8756469
Sent from the iBATIS - User - Java mailing list archive at Nabble.com.
me know.
Thanks!
--
View this message in context:
http://www.nabble.com/Deadlock-found-when-trying-to-get-lock--try-restarting-transaction-tf3157415.html#a8756469
Sent from the iBATIS - User - Java mailing list archive at Nabble.com.
Hi!
We are using apache ibatis with our MySQL 5.0 database (using innodb
tables), in our web application running on Tomcat 5. Recently we
started getting a number of errors relating to
java.sql.SQLException: Deadlock found when trying to get lock; Try
restarting transaction message from server
(SqlMapSessionImpl.java:85)
at
com.ibatis.sqlmap.engine.impl.SqlMapClientImpl.update(SqlMapClientImpl.java:62)
I am quite sure this is due to concurrent readings to
the BD table, but i don't know how to set or isue a
SET LOCK MODE TO WAIT; SET ISOLATION TO COMMITED
READ ( or dirty read
)
at
com.ibatis.sqlmap.engine.impl.SqlMapClientImpl.update(SqlMapClientImpl.java:62)
I am quite sure this is due to concurrent readings
to
the BD table, but i don't know how to set or isue a
SET LOCK MODE TO WAIT; SET ISOLATION TO COMMITED
READ ( or dirty read ) for the connections on the
DBCP
What is the class of
sqlMapper
?
-Henry
Ron Grabowski wrote:
Have you tried Larry's suggestion?
sqlMapper.executeUpdate(lockTable);
statement id=lockTable
lock table x in shared mode
/statement
--- Henry Lu [EMAIL PROTECTED] wrote:
Mr. Ruth, thank you very much for your info
How do i set sqlmap for the following SQL statement:
lock table x in shared mode
?
-Henry
How would you do it with JDBC?
On 6/23/05, Henry Lu [EMAIL PROTECTED] wrote:
How do i set sqlmap for the following SQL statement:
lock table x in shared mode
?
-Henry
Hi Henry,
Experts in iBATIS do read and answer questions on this board. The original creator of iBATIS frequents the list daily, in my experience.
However, that doesn't change the fact that this is an open source project. You are expected to try things out and report back with errors.
You are
16 matches
Mail list logo