2013-07-11 86 views
1

這是我的情況。我在我的客戶端的2個服務器全天候運行的應用程序:JBOSS 5 SQL Server嵌套異常

應用服務器:Tomcat的+ JBOSS 5 數據庫服務器:SQL Server 2008 R2的

最近我遇到一個錯誤,其中每個星期四早上我早上6點JBOSS打這個錯誤:

com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset by peer: socket write error 
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1368) 
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1355) 
at com.microsoft.sqlserver.jdbc.TDSChannel.write(IOBuffer.java:1548) 
at com.microsoft.sqlserver.jdbc.TDSWriter.flush(IOBuffer.java:2368) 
at com.microsoft.sqlserver.jdbc.TDSWriter.writePacket(IOBuffer.java:2270) 
at com.microsoft.sqlserver.jdbc.TDSWriter.endMessage(IOBuffer.java:1877) 
at com.microsoft.sqlserver.jdbc.TDSCommand.startResponse(IOBuffer.java:4403) 
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:386) 
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(SQLServerPreparedStatement.java:338) 
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:4026) 
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1416) 
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:185) 
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:160) 
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeUpdate(SQLServerPreparedStatement.java:306) 
at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeUpdate(WrappedPreparedStatement.java:365) 
at sun.reflect.GeneratedMethodAccessor343.invoke(Unknown Source) 
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 
at java.lang.reflect.Method.invoke(Method.java:597) 
at org.jboss.invocation.Invocation.performCall(Invocation.java:386) 
at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionContainer.java:228) 
at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:156) 
at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstanceInterceptor.java:173) 
at org.jboss.ejb.plugins.CallValidationInterceptor.invoke(CallValidationInterceptor.java:63) 
at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:121) 
at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:350) 
at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:181) 
at org.jboss.ejb.plugins.SecurityInterceptor.process(SecurityInterceptor.java:228) 
at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:211) 
at org.jboss.ejb.plugins.security.PreSecurityInterceptor.process(PreSecurityInterceptor.java:97) 
at org.jboss.ejb.plugins.security.PreSecurityInterceptor.invoke(PreSecurityInterceptor.java:81) 
at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:205) 
at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:138) 
at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:650) 
at org.jboss.ejb.Container.invoke(Container.java:1029) 
at sun.reflect.GeneratedMethodAccessor323.invoke(Unknown Source) 
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 
at java.lang.reflect.Method.invoke(Method.java:597) 
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) 
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) 
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) 
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) 
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) 
at org.jboss.invocation.unified.server.UnifiedInvoker.invoke(UnifiedInvoker.java:232) 
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891) 
at org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:744) 
at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:697) 
at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:551) 
at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:232) 

而且我的應用程序的服務給這個錯誤:

javax.ejb.EJBException: com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset by peer: socket write error; nested exception is: com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset by peer: socket write error: com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset by peer: socket write error; nested exception is: com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset by peer: socket write error: Connection reset by peer: socket write error 

我的客戶聲稱,重新是沒有活動正在做數據庫或應用程序服務器上星期四上午6點,因此我不知道是什麼觸發這個錯誤..它只發生在每週四早上6點。任何幫助,我非常感謝!

回答

0

什麼是網絡拓撲結構?前端和數據庫服務器之間是否有防火牆?如果是這樣,它可能是防火牆回收連接。