> hi dirk,
> I did some debugging on this problem.I found the exception occurs at
> public void start(Xid xid, int flags) method when the
> connection.setAutoCommit(false) is called in the JDBCDescriptorStore class
.
> An SQLException is raised with the error message set Update command is
not
> allowed
> in a multi-statement transaction .It looks like the setAutoCommit(false)
> should not be called
> explicitly by the programmer when dealing with a global transaction
> managed by an external
> transcation manager as it is implicitly set to false by the DataSource
> before returning the connection object.
> I commented out the setAutoCommit(false) part in the start method of the
> JDBCDescriptorStore and the base data was loaded successfully.
Good.
Am I right to assume that some DBs would start in auto-commit true ?
Maybe we can isolate the call to setAutoCommit(false) in a separate
try/catch, and ignore an exception being thrown there ?
Remy
