Getting locks in spring

[rajeevpariyadathu]

Hi All,

We have small application in spring, recieiving a string XML and parsing using sax parser and setting those values in objects.
While doing the load testing this simple application , we are getting the below lock information in the thread dump file many times. thats why our performance degrading and applicaiton fails.

Anybody have any idea, pls hlep.........lots of thanks in advance.


"http-8080-40" daemon prio=1 tid=0x000000005c99eb30 nid=0x16e3 waiting for monitor entry [0x0000000044e94000..0x0000000044e94d10]
at java.util.Hashtable.get(Hashtable.java:335)
- waiting to lock <0x00002b6f1144dc18> (a java.util.Properties)
at java.util.Properties.getProperty(Properties.java:7 74)
at org.springframework.web.servlet.mvc.multiaction.Pr opertiesMethodNameResolver.getHandlerMethodNameFor UrlPath(PropertiesMethodNameResolver.java:83)
at org.springframework.web.servlet.mvc.multiaction.Ab stractUrlMethodNameResolver.getHandlerMethodName(A bstractUrlMethodNameResolver.java:94)
at org.springframework.web.servlet.mvc.multiaction.Mu ltiActionController.handleRequestInternal(MultiAct ionController.java:371)
at org.springframework.web.servlet.mvc.AbstractContro ller.handleRequest(AbstractController.java:153)
at org.springframework.web.servlet.mvc.SimpleControll erHandlerAdapter.handle(SimpleControllerHandlerAda pter.java:45)
at org.springframework.web.servlet.DispatcherServlet. doDispatch(DispatcherServlet.java:798)
at org.springframework.web.servlet.DispatcherServlet. doService(DispatcherServlet.java:728)
at org.springframework.web.servlet.FrameworkServlet.p rocessRequest(FrameworkServlet.java:396)
at org.springframework.web.servlet.FrameworkServlet.d oPost(FrameworkServlet.java:360)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:637)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:717)
at org.apache.catalina.core.ApplicationFilterChain.in ternalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.do Filter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invo ke(StandardWrapperValve.java:233)
at org.apache.catalina.core.StandardContextValve.invo ke(StandardContextValve.java:191)
at org.apache.catalina.core.StandardHostValve.invoke( StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke (ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invok e(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.servic e(CoyoteAdapter.java:286)
at org.apache.coyote.http11.Http11Processor.process(H ttp11Processor.java:845)
at org.apache.coyote.http11.Http11Protocol$Http11Conn ectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run( JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:595)


thanks and regards,
Rajeev

[Alarmnummer]

It appears that someone is already holding a lock on the hashtable and that is why the other thread waits.. and waits.. and waits..

Can you see which thread already holds the lock? Perhaps you can log in with a profiler and see which thread is holding it. I guess you can also do it from with hprof, but I don't know the settings without documentation.