I am trying to resolve an issue we are have with the following error message:
com.ibm.db2.jcc.c.SqlException: The current transaction has been rolled back because of a deadlock or timeout. Reason code "68". at com.ibm.db2.jcc.c.lf.b(lf.java:3265) at com.ibm.db2.jcc.b.kb.i(kb.java:220) at com.ibm.db2.jcc.b.kb.a(kb.java:180) at com.ibm.db2.jcc.b.kb.a(kb.java:35) at com.ibm.db2.jcc.b.x.a(x.java:30) at com.ibm.db2.jcc.b.j.Gb(j.java:341) at com.ibm.db2.jcc.c.lf.R(lf.java:3099) at com.ibm.db2.jcc.b.d.f(d.java:1044) at com.ibm.db2.jcc.c.s.a(s.java:189) at com.ibm.db2.jcc.c.lf.c(lf.java:312) at com.ibm.db2.jcc.c.lf.next(lf.java:283) at com.ibm.ws.rsadapter.jdbc.WSJdbcResultSet.next(WSJdbcResultSet.java:2468 ) at com.ibatis.sqlmap.engine.execution.SqlExecutor.handleResults(SqlExecutor .java:380) at com.ibatis.sqlmap.engine.execution.SqlExecutor.handleMultipleResults(Sql Executor.java:301) at com.ibatis.sqlmap.engine.execution.SqlExecutor.executeQuery(SqlExecutor. java:190) at com.ibatis.sqlmap.engine.mapping.statement.GeneralStatement.sqlExecuteQu ery(GeneralStatement.java:205) at com.ibatis.sqlmap.engine.mapping.statement.GeneralStatement.executeQuery WithCallback(GeneralStatement.java:173) We are getting this a lot in out production system and we are running 2.3.0. We just rolled out the version with 2.3.0 today. Just wondering if this could be the result of IBATIS-458 or not. We only have the latest iBatis 2.3.2 jar in our trunk code. Thanks, Tom Henricksen Consultant Advanced Technologies Group, Inc.
