WebSphere 5.0.2.6 Application deployed is a pure struts application and is a soap client. When load test ran on this application on WebSphere there were several threads waiting to get a lock on a monitor. This caused the system hang. Do any of you have any idea about this ? -------------------------------------- Thread information: Thread type..................... Servlet handler name............................ Servlet.Engine.Transports : 1329 thread id....................... 0x3D361BD0 priority........................ 5 state........................... CW Waiting on monitor................ com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher@7718B840/7718B848 Waiting for web work............. no Executing web or local EJB work.. yes Waiting for remote orb work...... no Stack: com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward in WebAppRequestDispatcher.java native=false com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward in WebAppInvoker.java native=false com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook in WebAppInvoker.java native=false com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation in CachedInvocation.java native=false com.ibm.ws.webcontainer.cache.invocation.CacheableInvocationContext.invoke in CacheableInvocationContext.java native=false com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI in ServletRequestProcessor.java native=false com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service in OSEListener.java native=false com.ibm.ws.webcontainer.http.HttpConnection.handleRequest in HttpConnection.java native=false com.ibm.ws.http.HttpConnection.readAndHandleRequest in HttpConnection.java native=false com.ibm.ws.http.HttpConnection.run in HttpConnection.java native=false com.ibm.ws.util.ThreadPool$Worker.run in ThreadPool.java native=false --------------------------------------