|
From this,
java.sql.SQLException: Transaction state not valid.
at com.ibm.as400.access.JDError.throwSQLException(JDError.java:360)
at com.ibm.as400.access.AS400JDBCConnection.setReadOnly(AS400JDBCConnection.java:2885)
I'd check to see if journaling is on.
Now, I suppose it could also fail if there were exclusive locks, but from what you sent, no journaling would be my first guess.
Today I did some research on the "Transaction state not valid" issue, it seems related to record lock logic in database level. this error was generally caused by an performing an update operation on a locked result set. or update a non update-able resultset etc. it's really depends on what they did in the transaction. I guess may be the database lock logic is little different from DB2 LUW and DB2 for System i, so their code run into some kind of dead lock, which caused the exception.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.