配置期间超过了 WebLogic Server StuckThreadMaxTime 值

配置期间超过了 WebLogic Server StuckThreadMaxTime 值

如果正在使用配置程序配置 WebLogic Server 9.2 MP2 或 10，并且完成配置花费的时间超过 600 秒，则会将以下错误返回到终端、WebLogic Server 域和服务器日志：

<Error> <WebLogicServer> <BEA-000337> <[STUCK] Exe 
cuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy 
for "681" seconds working on the request "Http Request: /opensso/setup/setSetup 
Progress", which is more than the configured time (StuckThreadMaxTime) of "600" 
seconds. Stack trace: ... 

产生此错误是由于 WebLogic Server 超过了其“阻塞线程最长时间：”的默认值：600 秒。

解决方法。如果配置程序没有响应，则重新启动。同时，考虑将 WebLogic Server 的“阻塞线程最长时间”的值从默认的 600 秒更改为更大的值，例如 1200 秒。使用 WebLogic 控制台更改该值（base_domain >“环境”>“服务器”>“管理服务器”>“配置/调节”）。

<!-- END PC11 COMPONENT V.0 --><!-- BEGIN D8 COMPONENT V.1 -->

评论

1 楼 carrey360 2012-04-19  

我也遇到这问题<Error> <WebLogicServer> <BEA-000337> <[STUCK]
ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)' has been b
usy for "647" seconds working on the request "Http Request: /usermanage/statSAP.
jsp", which is more than the configured time (StuckThreadMaxTime) of "600" secon
ds. Stack trace:
        com.sap.mw.jco.rfc.MiddlewareRFC$Client.nativeExecute(Native Method)
        com.sap.mw.jco.rfc.MiddlewareRFC$Client.execute(MiddlewareRFC.java:1244)

        com.sap.mw.jco.JCO$Client.execute(JCO.java:3842)
        com.sap.mw.jco.JCO$Client.execute(JCO.java:3287)
        com.buptol.webservice.xibeiusertrainstatics.addStatInfo(xibeiusertrainst
atics.java:434)
        jsp_servlet._usermanage.__statsap._jspService(__statsap.java:108)
        weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
        weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(St
ubSecurityHelper.java:225)
        weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityH
elper.java:127)
        weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:2
83)
        weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
        weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:
42)
        com.buptol.filter.SignOnFilter.doFilter(SignOnFilter.java:99)
        weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:
42)
        com.buptol.filter.EncodingFilter.doFilter(EncodingFilter.java:59)
        weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:
42)
        weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.r
un(WebAppServletContext.java:3212)
        weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu
bject.java:321)
        weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121
)
        weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServ
letContext.java:1983)
        weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletCont
ext.java:1890)
        weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java
:1344)
        weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
        weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
>
除了上述这种办法还有别的方法吗