| Pooja |
Wed Dec 26 08:32:31 GMT 2007 |
| |
Hi,
We are using primrose(v 2.7.0). We are getting the following errors very often:
Type: General Database Error
Message: Invalid state, the Connection object is closed.
Exception:
java.sql.SQLException: Invalid state, the Connection object is closed.
at net.sourceforge.jtds.jdbc.TdsCore.checkOpen(TdsCore.java:440)
at net.sourceforge.jtds.jdbc.TdsCore.clearResponseQueue(TdsCore.java:715)
at net.sourceforge.jtds.jdbc.JtdsStatement.initialize(JtdsStatement.java:544)
at net.sourceforge.jtds.jdbc.JtdsPreparedStatement.executeQuery(JtdsPreparedStatement.java:663)
at uk.org.primrose.pool.core.PoolPreparedStatement.executeQuery(PoolPreparedStatement.java:59)
at PendingWireAction.getPendingWireActionsAfterModifiedDate(PendingWireAction.java:851)
Type: General Database Error
Message: Invalid state, the ResultSet object is closed.
Exception:
java.sql.SQLException: Invalid state, the ResultSet object is closed.
at net.sourceforge.jtds.jdbc.JtdsResultSet.checkOpen(JtdsResultSet.java:295)
at net.sourceforge.jtds.jdbc.JtdsResultSet.next(JtdsResultSet.java:555)
at uk.org.primrose.pool.core.PoolResultSet.next(PoolResultSet.java:52)
at PendingWireAction.getPendingWireActionsAfterModifiedDate(PendingWireAction.java:851)
Both the code paths are called from a daemon (unix user) process.
Any idea about this? Thanks in advance.
-Pooja
|
| |
| sedj |
Sun Dec 30 11:47:50 GMT 2007 |
| |
As I'm sure you can appreciate, without seeing any actual code, its hard to tell what the problem is.
All I can say is that it looks like you are accessing objects such as a ResultSet after it has already been closed ... |
