Skip to Content
author's profile photo Former Member
Former Member

Thread is waiting to get a lock

Hi all

I have a question I'd like have an answer for: In my company we are in the verge of delivering a project based on a SAP NetWeaver app which uses Crystal Reports to display the reports to be used by the end users. We have server for this NetWeaver Portal app and a different server for the BOE Server. The webserver is installed on the same server as the NetWeaver app.

We have a problem, which our team supposes is related in some way with the Webserver: We have watched that the heap memory in the server starts growing and goes higher with time, so the server starts having problem because of it. Our NetWeaver team detected by using the SAP Management Console, that there are 3 threads which remain waiting to get a lock (i.e.: for up to 64 hours last weekend). One of them is related to Crystal Reports and the other two are not (we suppose as we can't see something pointing at it):

I'm including some fragments of the 3 threads' logs

Thread 1:

Thread 'HTTP Worker ', process 'server0', index '254'

"HTTP Worker " Id=165 WAITING_FOR_LOCK

cpu=19474.97 ms (system=686.34 / user=18788.63) allocated=4440507800 B

user="Guest" sessionId="323080501" requestId="8382"

application="JavaEE/CrystalReports"

Thread is waiting to get a lock: waiting for monitor lock com.sap.engine.session.exec.ClientContextImpl (addr=0x000000012ba2e038)

held by "HTTP Worker " Id=154

at com.sap.engine.session.exec.ClientContextImpl.addThreadReference()V(ClientContextImpl.java:607)

at

Thread 2:

Thread 'HTTP Worker ', process 'server0', index '242'

"HTTP Worker " Id=154 WAITING_FOR_LOCK

cpu=44406.59 ms (system=1146.62 / user=43259.97) allocated=33645176768 B

user="Guest" sessionId="323080501" requestId="8383"

Thread is waiting to get a lock: waiting for monitor lock java.lang.String (addr=0x000000012bb16e10)

held by "HTTP Worker " Id=165

at com.sap.engine.session.exec.ClientContextImpl.destroy()V(ClientContextImpl.java:730)

at

Thread 3:

Thread 'Session mangement task', process 'server0', index '425'

"Session mangement task" Id=251 WAITING_FOR_LOCK

cpu=684.87 ms (system=4.82 / user=680.05) allocated=28398688 B

Thread is waiting to get a lock: waiting for monitor lock com.sap.engine.session.runtime.http.HttpRuntimeSessionModel (addr=0x0000000116889678)

held by "HTTP Worker " Id=165

at com.sap.engine.session.runtime.RuntimeSessionModel.release(Ljava.lang.Object;)V(RuntimeSessionModel.java:474)

We would thank you for any advise you might have on this regard.

Gabriel Sánchez Valdez

Neoris de México SA de CV

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Posted on Apr 14, 2011 at 05:31 PM

    Gabriel

    Please Upgrade the Engine of the j2ee server to the latest version.

    SWC= J2EE ENGINE SERVERCORE

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.