BEA-000337

<2009-7-10 下午05时46分07秒 CST> <Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "704" seconds working on the request "Http Request: /mm5/graph/getdata.jsp", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
        java.net.SocketInputStream.socketRead0(Native Method)
        java.net.SocketInputStream.read(SocketInputStream.java:129)
        weblogic.jdbc.sqlserver.SQLServerByteOrderedDataReader.makeMoreDataAvailable(Unknown Source)
        weblogic.jdbc.sqlserver.SQLServerByteOrderedDataReader.getArrayOfBytes(Unknown Source)
        weblogic.util.UtilPagedTempBuffer.write(Unknown Source)
        weblogic.jdbc.sqlserver.SQLServerColumn.cacheLongData(Unknown Source)
        weblogic.jdbc.sqlserver.tds.TDSRequest.getColumnDataForRow(Unknown Source)
        weblogic.jdbc.sqlserver.SQLServerImplResultSet.getData(Unknown Source)
        weblogic.jdbc.base.BaseResultSet.getBinaryStream(Unknown Source)
        weblogic.jdbc.base.BaseResultSet.getBinaryStream(Unknown Source)
        weblogic.jdbc.wrapper.ResultSet_weblogic_jdbc_base_BaseResultSet.getBinaryStream(Unknown Source)
        jsp_servlet._graph.__getdata._jspService(__getdata.java:177)
        weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
        weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
        weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
        weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
        weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
        weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3370)
        weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
        weblogic.security.service.SecurityManager.runAs(Unknown Source)
        weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2117)
        weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2023)
        weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1359)
        weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
        weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
>

Connection reset by peer: socket write error
这个跟数据库没有关系，当客户端发出请求（request）后，如果还没有完全获得服务端的响应（response），客户端与服务器段的连接断开（例如断网、按了“停止”按钮、或者客户端浏览器关闭等），服务器端就会抛出此Exception。


Causes and solutions
This exception occurs when a client made a request, and before receiving the full response, either of the following happened:

client's browser has been closed.
client's connection has been disconnected.
client presses the stop button.
This exception is normally harmless. It does not seem possible to trap this exception with J2SE.

Connection reset by peer的原因：
经常出现的Connection reset by peer: 原因可能是多方面的，不过更常见的原因是：
①：服务器的并发连接数超过了其承载量，服务器会将其中一些连接Down掉；
②：客户关掉了浏览器，而服务器还在给客户端发送数据；
③：浏览器端按了Stop

评论

1 楼 gxliang 2010-08-30  

BEA-000337 这个通常要打个补丁，一般是在AIX的JVM结合weblogic出现的。