Hi James,
Will looking at the journals tell us anything?
Maybe. Worth checking out. I'd look for anything that happened around
that time. Depending on how the application is running, like standalone or
web app, there may be other areas to check: Server logs and even QSysopr
messages.
SQLException can have chained warnings and messages, sort of like second
level detail on AS/400 messages, but the app has to program appropriately
for them. See this portion of my 11 year old (!!!) tutorial:
JDBC Exception Types and Exception Handling
http://java.sun.com/developer/onlineTraining/Database/JDBC20Intro/JDBC20.html#JDBC209
which would probably give needed info, but most programs effectively swallow
or ignore them, especially warnings.
If this is happening sporadically, I would check for record locks by
other applications. If it happens every time, I don't have a specific area
to point to other than maybe a program bug in terms of previous or current
transaction state. Don't know if this is third party or not, but if so, I'd
check with them.
HTH,
Joe Sam
Joe Sam Shirah - www.conceptgo.com (904) 302-6870
conceptGO - Consulting/Development/Outsourcing
Java Filter Forum: www.ibm.com/developerworks/java
Just the JDBC FAQs: www.jguru.com/faq/JDBC
Going International? www.jguru.com/faq/I18N
Que Java400? www.jguru.com/faq/Java400
-----Original Message-----
From: James Lampert
Sent: Tuesday, July 10, 2012 2:24 PM
To: Java Programming on and around the IBM i
Subject: Re: Anybody here have any experience running Rollbase on a
V6box?(cross-posted)
Joe Sam Shirah wrote:
Hi James,
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.
Journaling is on.
We just got the same failure here.
Will looking at the journals tell us anything? If so, what should I look
for?
--
JHHL
-- 8
midrange.com
