JBoss SQLException - Invalid state, the Connection object is closed

[Sw Ja]

Hi,

I am getting the attached error in Production system

WARN  [org.jboss.util.NestedThrowable] Duplicate throwable nesting of same base type: class org.jboss.mq.SpyJMSException is assignable from: class org.jboss.mq.SpyJMSException
2017-01-18 14:25:42,107 ERROR [org.jboss.jms.asf.StdServerSession] failed to commit/rollback
org.jboss.mq.SpyXAException: Resource manager error during commit; - nested throwable: (org.jboss.mq.SpyJMSException: Could not rollback tx: 80292; - nested throwable: (java.sql.SQLException: Invalid state, the Connection object is closed.))
at org.jboss.mq.SpyXAException.getAsXAException(SpyXAException.java:72)
at org.jboss.mq.SpyXAResource.commit(SpyXAResource.java:92)
at org.jboss.jms.asf.StdServerSession.onMessage(StdServerSession.java:317)
at org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessage(SpyMessageConsumer.java:905)
at org.jboss.mq.SpyMessageConsumer.addMessage(SpyMessageConsumer.java:170)
at org.jboss.mq.SpySession.run(SpySession.java:323)
at org.jboss.jms.asf.StdServerSession.run(StdServerSession.java:194)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.jboss.mq.SpyJMSException: Could not rollback tx: 80292; - nested throwable: (java.sql.SQLException: Invalid state, the Connection object is closed.)
at org.jboss.mq.pm.jdbc2.PersistenceManager.rollbackPersistentTx(PersistenceManager.java:988)
at org.jboss.mq.pm.Tx.rollback(Tx.java:258)
at org.jboss.mq.pm.TxManager.rollbackTx(TxManager.java:180)
at org.jboss.mq.server.JMSDestinationManager.transact(JMSDestinationManager.java:449)
at org.jboss.mq.server.JMSServerInterceptorSupport.transact(JMSServerInterceptorSupport.java:126)
at org.jboss.mq.security.ServerSecurityInterceptor.transact(ServerSecurityInterceptor.java:197)
at org.jboss.mq.server.TracingInterceptor.transact(TracingInterceptor.java:352)
at org.jboss.mq.server.JMSServerInvoker.transact(JMSServerInvoker.java:132)
at org.jboss.mq.il.jvm.JVMServerIL.transact(JVMServerIL.java:175)
at org.jboss.mq.Connection.send(Connection.java:1110)
at org.jboss.mq.SpyXAResourceManager.commit(SpyXAResourceManager.java:166)
at org.jboss.mq.SpyXAResource.commit(SpyXAResource.java:88)
... 7 more
Caused by: java.sql.SQLException: Invalid state, the Connection object is closed.
at net.sourceforge.jtds.jdbc.ConnectionJDBC2.checkOpen(ConnectionJDBC2.java:1634)
at net.sourceforge.jtds.jdbc.ConnectionJDBC2.prepareStatement(ConnectionJDBC2.java:2366)
at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.doPrepareStatement(BaseWrapperManagedConnection.java:349)
at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.prepareStatement(BaseWrapperManagedConnection.java:344)
at org.jboss.resource.adapter.jdbc.WrappedConnection.prepareStatement(WrappedConnection.java:187)
at org.jboss.mq.pm.jdbc2.PersistenceManager.removeMarkedMessages(PersistenceManager.java:880)
at org.jboss.mq.pm.jdbc2.PersistenceManager.rollbackPersistentTx(PersistenceManager.java:972)
... 18 more




After restarting the services, Issue is resolved.


Can anyone advise what is the problem and what can be done to fix it ?

[Knute Snortum]

It's hard to know but I would guess the connection timed out.  Do you have very long SQL calls?  Can you shorten them?  Can you increase the connection timeout parameter?

[Dave Tolls]

I thin you'd get a socket closed error, rather than a connection closed.
That implies to me that close() has been called (at some point) on that connection.

Though it could simply be a rubbish exception text.