2024年5月1日发(作者：)

Weblogic日志中的报错

第一

####

<[ACTIVE] ExecuteThread: '6' for queue: 't (self-tuning)'>

<> <> <> <13>

<[ServletContext@57155715 - appName: 'mes-hotrolling-app',

name: '', context-path: '/mes-hotrolling-app', version: 2011042505] Servlet

failed with Exception

lStateException: Response already committed

at IfCommitted

(:1422)

at ror(:580)

at ror(:559)

at FlexClientStreaming

OpenRequest(:732)

at eStreamingRequest

(:1022)

at e

(:430)

at e(:322)

at e(:856)

at curityHelper$

(:227)

at Servlet(:125)

at e(:283)

at er(:26)

at er(:42)

at er

(:99)

at er(:42)

at er(:413)

at er(:42)

at ServletContext$

(:3242)

at (:321)

at (:121)

at dExecute

(:2010)

>

at e

(:1916)

at (:1366)

at e(:209)

at (:181)

注：这个错误发生了好几次，是跟自动仓储相关的，使用的是Flex的消息推送机制导致的，

原因待查。

原因分析

这个原因主要是请求重复提交。

第二

####

<[ACTIVE] ExecuteThread: '15' for queue: 't (self-tuning)'>

<> <> <> <13> <[STUCK] ExecuteThread: '56' for

queue: 't (self-tuning)' has been busy for "715" seconds working on the

request "Http Request: /mes-hotrolling-app/messagebroker/streamingamf", which is more than the

configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:

注：自动仓储flex消息推送超时，待查。

原因分析

造成这种stuck线程超时的主要原因是这个线程个活动的时间太长了，远远超过了weblogic

中设置的600秒得时间。修改weblogic的默认时间不是解决问题的根本。根本还要从代码

的执行效率上下功夫。

第三

####

<[ACTIVE] ExecuteThread: '13' for queue: 't (self-tuning)'> <

Kernel>> <> <> <13>

message during the configured timeout value. The socket has been closed.>

注：类似这个错误发生了好几次，可能是用户选择某项功能后，未等服务器返回结果即关闭