9 Replies Latest reply: May 13, 2011 10:14 AM by Lukas Weigelt RSS

LockException / failed to acquire exclusive lock on client session

Lukas Weigelt
Currently Being Moderated

Hi guys... in continuation to Portal Runtime Error

 

When trying to preview/show  a WD4A which has shortly been transported from QS to PROD we are getting the error

"LockException / failed to acquire exclusive lock on client session"

 

on QS this doesn't occur. Both Systems (Portal QS+ HCM QS AND Portal PROD + HCM PROD) are on equal Systems and SPs

 

I checked the following notes:

 

1180508 (doesn't really help)

1234847 (supposedly doesn't apply as the Application is WD4A)

 

I checked thread /thread/1596510 [original link is broken] and thus made our basis guys check the Databases, all is fine (supposedly, this is outside of my reference).

 

Detailed error Log:

 

Exception occured during processing of Web Dynpro application sap.com/pb/PageBuilder. The causing exception is nested. 
[EXCEPTION]
 com.sap.tc.webdynpro.services.session.LockException: Thread SAPEngine_Application_Thread[impl:3]_7 failed to acquire exclusive lock on client session ClientSession(id=(J2EE317770400)ID0741190250DB44961f08fcc5c2790ca21b628b7e6b4258207430End_488588755). Existing locks: LockingManager(ThreadName:SAPEngine_Application_Thread[impl:3]_7, exclusive client session lock: ClientSessionLock(SAPEngine_Application_Thread[impl:3]_12), shared client session locks: ClientSessionSharedLockManager([]), app session locks: ApplicationSessionLockManager([]), current request: sap.com/pb/PageBuilder).Hint: Take a thread dump of the server node to find the blocking thread that causes the problem.
     at com.sap.tc.webdynpro.clientserver.session.ClientSession$LockingManager.lock(ClientSession.java:1539)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:236)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

 

best regards.... Lukas...

Actions