]捕获SQLException，SQLState HY010代码：0-假设检测到死锁，请尝试：8 java.sql.SQLException:无效状态，连接对象已关闭

我在defaultDS中从与MSSQL 2008连接的Jboss 4.3.2GA中获得此异常。在最近两周的环境中，发生了两次此错误并停止了消息传递

有MDB正在侦听主题，消息传递突然停止，JMS表中没有消息（甚至错误队列中也没有消息）。所有的信息都丢失了。试图找到根本原因

请谈谈你对此的看法

2017-06-12 22:52:39,487 WARN  [org.jboss.messaging.core.impl.JDBCSupport] Trying again after a pause
2017-06-12 22:52:39,764 WARN  [org.jboss.messaging.core.impl.JDBCSupport] SQLException caught, SQLState HY010 code:0- assuming deadlock detected, try:8
java.sql.SQLException: Invalid state, the Connection object is closed.
               at net.sourceforge.jtds.jdbc.ConnectionJDBC2.checkOpen(ConnectionJDBC2.java:1494)
               at net.sourceforge.jtds.jdbc.ConnectionJDBC2.prepareStatement(ConnectionJDBC2.java:2215)
               at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.doPrepareStatement(BaseWrapperManagedConnection.java:449)
               at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.prepareStatement(BaseWrapperManagedConnection.java:444)
               at org.jboss.resource.adapter.jdbc.WrappedConnection.prepareStatement(WrappedConnection.java:243)
               at org.jboss.messaging.core.impl.JDBCPersistenceManager$1AddReferenceRunner.doTransaction(JDBCPersistenceManager.java:1337)
               at org.jboss.messaging.core.impl.JDBCSupport$JDBCTxRunner2.execute(JDBCSupport.java:474)
               at org.jboss.messaging.core.impl.JDBCSupport$JDBCTxRunner2.executeWithRetry(JDBCSupport.java:512)
               at org.jboss.messaging.core.impl.JDBCPersistenceManager.addReference(JDBCPersistenceManager.java:1408)
               at org.jboss.messaging.core.impl.ChannelSupport.handle(ChannelSupport.java:227)
               at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.routeInternal(MessagingPostOffice.java:2212)
               at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.route(MessagingPostOffice.java:499)
               at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.sendMessage(ServerConnectionEndpoint.java:763)
               at org.jboss.jms.server.endpoint.ServerSessionEndpoint.send(ServerSessionEndpoint.java:399)
               at org.jboss.jms.server.endpoint.advised.SessionAdvised.org$jboss$jms$server$endpoint$advised$SessionAdvised$send$aop(SessionAdvised.java:87)
               at org.jboss.jms.server.endpoint.advised.SessionAdvised$send_7280680627620114891.invokeNext(SessionAdvised$send_7280680627620114891.java)
               at org.jboss.jms.server.container.SecurityAspect.handleSend(SecurityAspect.java:157)
               at sun.reflect.GeneratedMethodAccessor92.invoke(Unknown Source)
               at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
               at java.lang.reflect.Method.invoke(Method.java:597)
               at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:121)
               at org.jboss.jms.server.endpoint.advised.SessionAdvised$send_7280680627620114891.invokeNext(SessionAdvised$send_7280680627620114891.java)
               at org.jboss.jms.server.endpoint.advised.SessionAdvised.send(SessionAdvised.java)
               at org.jboss.jms.wireformat.SessionSendRequest.serverInvoke(SessionSendRequest.java:95)
               at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143)
               at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:862)
               at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:609)
               at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:421)
               at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:174)
2017-06-12 22:52:39,764 WARN  [org.jboss.messaging.core.impl.JDBCSupport] Trying again after a pause

---

你试过了吗？谢谢你的快速回复，我发现了相同的链接，但对建议的解决方案有点担心。我觉得我得到的错误是，当JBoss试图将消息持久化到JMS数据库时，抛出了异常（我从跟踪中了解到）。建议的解决方案是关于何时从JMS数据库读取消息？您尝试过了吗？感谢您的快速响应，我发现了相同的链接，但有点担心建议的解决方案。我觉得我得到的错误是，当JBoss试图将消息持久化到JMS数据库时，抛出了异常（我从跟踪中了解到）。建议的解决方案是关于何时从JMS数据库读取消息？