Hi ,
We are currently having this version of Documentum deployed in our weblogic cluster environment.
DA -> 6.7 sp1 , WEBTOP -> 6.7 sp1 , DFS -> 6.7 sp1 and MDD -> 6.7 sp1
There is a Holding lock problem i am facing with the stuck thread inside Documentum
the application of thread stuck in Documentum
I think that it is DocumentumWebTop since the package is com.documentum.web
If it were another form kindly let me know what could be the reason
WebLogic brand as stuck threads that are running for more than 600 seconds, which is a very high time for a transactional environment
In the event that it is remote calls, we recommend that you implement the appropriate timeout
error trace:
<Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '1 'for queue:' weblogic.kernel.Default (self-tuning) 'has been busy for "645" second
s working on the request "weblogic.servlet.internal.ServletRequestImpl @ 181e38c8 [
POST / da / wdk / container / HTTP/1.1 combocontainer.jsp
Accept: image / jpeg, application / x-ms-application, image / gif, application / xaml + xml, image / pjpeg, application / x-ms-xbap, application / x-shockwave-flash /
Referer: http://......./da/wdk/container/combocontainer.jsp
Accept-Language: en-US
Content-Type: application / x-www-form-urlencoded
User-Agent: Mozilla/4.0 (compatible, MSIE 7.0, Windows NT 6.1; Trident/4.0; GBS - D80P11; UT_GBS - con624; SLCC2.; NET CLR 2.0.50727;. NET CLR 3.5.30729;. NET CLR 3.0. 30729, Med ia Center PC 6.0, MS-RTC LM 8; chromeframe/21.0.1180.83)
Accept-Encoding: gzip, deflate
Content-Length: 1237
Cache-Control: no-cache
Cookies: d6_wdk_pref0= ..........
Connection: Keep-Alive
Proxy-Client-IP: .......
X-Forwarded-For: .......
X-WebLogic-KeepAliveSecs: 30
X-WebLogic-Request-ClusterInfo: true
x-weblogic-cluster-hash:........
]", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
Thread-21 "[STUCK] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'" <alive, in native, suspended, priority=1, DAEMON> { sun.nio.ch.SocketDispatcher.read1(SocketDispatcher.java:???) sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:46) sun.nio.ch.IOUtil.read(IOUtil.java:197) sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:152) ^-- Holding lock: java.lang.Object@144958e7[thin lock] com.documentum.fc.impl.util.io.MessageChannel.readSocket(MessageChannel.java:121) com.documentum.fc.impl.util.io.MessageChannel.readLength(MessageChannel.java:99) com.documentum.fc.impl.util.io.MessageChannel.getIncomingMessageLength(MessageChannel.java:91) com.documentum.fc.impl.util.io.MessageChannel.read(MessageChannel.java:77) ^-- Holding lock: com.documentum.fc.impl.util.io.MessageChannel@14494e9e[thin lock] com.documentum.fc.client.impl.connection.netwise.AbstractNetwiseRpcClient.receiveMessage(AbstractNetwiseRpcClient.java:177) com.documentum.fc.client.impl.connection.docbase.netwise.NetwiseDocbaseRpcClient.applyForId(NetwiseDocbaseRpcClient.java:523) ^-- Holding lock: com.documentum.fc.client.impl.connection.docbase.netwise.NetwiseDocbaseRpcClient@14494dc5[thin lock] com.documentum.fc.client.impl.connection.docbase.DocbaseConnection$5.evaluate(DocbaseConnection.java:1233) ^-- Holding lock: com.documentum.fc.client.impl.connection.docbase.DocbaseConnection@182e8361[fat lock] com.documentum.fc.client.impl.connection.docbase.DocbaseConnection.evaluateRpc(DocbaseConnection.java:1025) ^-- Holding lock: com.documentum.fc.client.impl.connection.docbase.DocbaseConnection@182e8361[fat lock] com.documentum.fc.client.impl.connection.docbase.DocbaseConnection.applyForId(DocbaseConnection.java:1227) com.documentum.fc.client.impl.docbase.DocbaseApi.makeLoad(DocbaseApi.java:790) com.documentum.fc.client.impl.DfLoadRecord.save(DfLoadRecord.java:29) com.documentum.fc.client.impl.DfLoadRecord___PROXY.save(DfLoadRecord___PROXY.java:???) com.documentum.dmcl.impl.SaveHandler.exec(SaveHandler.java:20) com.documentum.dmcl.impl.DmclApi.exec(DmclApi.java:110) com.documentum.dmcl.impl.DmclApi.exec(DmclApi.java:103) com.documentum.fc.client.impl.session.Session.apiExec(Session.java:2850) com.documentum.fc.client.impl.session.SessionHandle.apiExec(SessionHandle.java:1737) com.documentum.webcomponent.admin.utilities.ApiTester.executeCommands(ApiTester.java:152) com.documentum.webcomponent.admin.utilities.ApiTester.onClickExecute(ApiTester.java:141) sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:???) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:27) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:575) com.documentum.web.form.FormProcessor.invokeMethod(FormProcessor.java:1517) com.documentum.web.form.FormProcessor.invokeMethod(FormProcessor.java:1500) com.documentum.web.form.FormProcessor.fireActionEvent(FormProcessor.java:1262) com.documentum.web.form.RecallOperation.execute(RecallOperation.java:74) com.documentum.web.form.FormProcessor.processAction(FormProcessor.java:69) com.documentum.web.form.FormAction.processAction(FormAction.java:71) com.documentum.web.env.WDKController.doStartRequest(WDKController.java:156) com.documentum.web.env.WDKController.processRequest(WDKController.java:95) com.documentum.web.env.WDKController.doFilter(WDKController.java:71) weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:55) weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3656) weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650) weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:308) weblogic.security.service.SecurityManager.runAs(SecurityManager.java:117) weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2204) weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2126) weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1412) weblogic.work.ExecuteThread.execute(ExecuteThread.java:198) weblogic.work.ExecuteThread.run(ExecuteThread.java:165) }
Could someone explain how i can move forward in fixing the timeout problem.
Thanks in advance
Thanks
Xavier
