Re: "Cursor state not valid.", AS400 JDBC, IBM JTOpen 3.0
Sunday, April 28, 2002 02:10 PM
I resolved the "Cursor state not valid" message.
Here is how I did it:
I discovered that my homegrown JDBC connection pool was not thread safe. It turned out that multiple threads were simultaneously using a java.sql.Connection object.
I cleaned up the threading issue. My app can now run SELECT statements without a hitch.