有关“Connection reset by peer: socket write error”的错误,导致WAS5死掉!

Annjo 2005-07-14 10:29:39
服务器上装有WAS5.0,数据库和应用程序安装在同一台服务器上,采用JDBC数据源,程序在执行提交修改某个文本编辑的内容时,日志中出现以下错误(错误只针对个别修改):
[05-7-14 9:52:27:750 CST] 2531a47e RequestProces I org.apache.struts.action.RequestProcessor Processing a 'POST' for path '/StaticFile'
[05-7-14 9:52:27:766 CST] 2531a47e SystemOut O java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]The DBMS returned an unspecified error.
[05-7-14 9:52:27:781 CST] 2531a47e StaleConnecti A CONM7007I: 将以下 ErrorCode 为 0 且 SQLState 为 08S01 的 SQLException 映射到 StaleConnectionException:java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Connection reset by peer: socket write error
at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.microsoft.jdbc.sqlserver.tds.TDSRPCRequest.submitRequest(Unknown Source)
at com.microsoft.jdbc.sqlserver.tds.TDSCursorRequest.openCursor(Unknown Source)
at com.microsoft.jdbc.sqlserver.SQLServerImplStatement.execute(Unknown Source)
at com.microsoft.jdbc.base.BaseStatement.commonExecute(Unknown Source)
at com.microsoft.jdbc.base.BaseStatement.executeQueryInternal(Unknown Source)
at com.microsoft.jdbc.base.BasePreparedStatement.executeQuery(Unknown Source)
at com.microsoft.jdbcx.base.BasePreparedStatementWrapper.executeQuery(Unknown Source)
at com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.executeQuery(WSJdbcPreparedStatement.java:426)
at com.harmony.dao.SubjectColumnDAO.get(SubjectColumnDAO.java:281)
at com.harmony.dao.SubjectColumnDAO.get(SubjectColumnDAO.java:265)
at com.harmony.dao.SubjectColumnDAO.getSubjectName(SubjectColumnDAO.java:788)
at com.harmony.action.StaticFileAction.execute(StaticFileAction.java:144)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:446)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:266)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1292)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:510)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:974)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:555)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:200)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:119)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:276)
at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
at com.ibm.ws.webcontainer.cache.invocation.CacheableInvocationContext.invoke(CacheableInvocationContext.java:114)
at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:186)
at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:618)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:443)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:593)

[05-7-14 9:52:27:781 CST] 2531a47e ConnectionEve A J2CA0056I: 连接管理器接收到来自资源 jdbc/pkportal 的资源适配器的致命连接错误。接收到的异常为 com.ibm.websphere.ce.cm.StaleConnectionException: [Microsoft][SQLServer 2000 Driver for JDBC]Connection reset by peer: socket write error
[05-7-14 9:52:27:797 CST] 2531a47e SystemOut O com.ibm.websphere.ce.cm.StaleConnectionException: [Microsoft][SQLServer 2000 Driver for JDBC]Connection reset by peer: socket write error

以上的错误会使WAS5.0死掉,但WAS5.1不死,不知道是什么原因导致这种错误,请各位高手帮帮忙~!
...全文
2902 4 打赏 收藏 转发到动态 举报
写回复
用AI写文章
4 条回复
切换为时间正序
请发表友善的回复…
发表回复
Annjo 2005-07-21
  • 打赏
  • 举报
回复
搞定了,是数据库补丁的问题,将sp4补丁卸掉,装上sp3a就不出现这个问题了,至于原因I don't know!
Annjo 2005-07-18
  • 打赏
  • 举报
回复
[05-7-14 9:52:27:766 CST] 2531a47e SystemOut O java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]The DBMS returned an unspecified error.
主要是这个错误,郁闷的是,这个错误在有些机子的测试环境下居然不发生~~~
Annjo 2005-07-18
  • 打赏
  • 举报
回复
奇怪的是,采用ODBC数据源连接时,不出现这种错误,而采用JDBC则出现这种错误,又或者当采用JDBC数据源连接,改变文本输入框(是个文本编辑器)的内容,则有时会出现这个错误,有时又不出现这个错误,原来以为和输入的字符有关,但经测试这个可能排除,因为在运行正常的情况下,有时增加或减少一个中文汉字,也会出现这种情况,真的不知道真正的问题出在哪儿???
hoho1979 2005-07-17
  • 打赏
  • 举报
回复
可能与数据库的并发处理有关

2,633

社区成员

发帖
与我相关
我的任务
社区描述
WebSphere 是 IBM 的软件平台。它包含了编写、运行和监视全天候的工业强度的随需应变 Web 应用程序和跨平台、跨产品解决方案所需要的整个中间件基础设施,如服务器、服务和工具。
社区管理员
  • WebSphere社区
加入社区
  • 近7日
  • 近30日
  • 至今
社区公告
暂无公告

试试用AI创作助手写篇文章吧