Our application currently uses Hibernate 3.0.5 and JOTM. We've noticed that in testing Hibernate 3.2 CR 1, we see performance degradation. Many of the threads run into a lock contention issue, similar to the following:
Code:
at sun.net.www.protocol.jar.JarFileFactory.get(Unknown Source)
- waiting to lock <0x2da8f980> (a sun.net.www.protocol.jar.JarFileFactory)
at sun.net.www.protocol.jar.JarURLConnection.connect(Unknown Source)
at sun.net.www.protocol.jar.JarURLConnection.getInputStream(Unknown Source)
at sun.misc.URLClassPath$Loader.getResource(Unknown Source)
at sun.misc.URLClassPath.getResource(Unknown Source)
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at org.mortbay.http.ContextLoader.loadClass(ContextLoader.java:197)
at org.mortbay.http.ContextLoader.loadClass(ContextLoader.java:170)
at org.objectweb.carol.jndi.lmi.LmiInitialContext.resolveObject(LmiInitialContext.java:95)
at org.objectweb.carol.jndi.lmi.LmiInitialContext.lookup(LmiInitialContext.java:157)
at javax.naming.InitialContext.lookup(Unknown Source)
at org.objectweb.carol.jndi.spi.MultiContext.lookup(MultiContext.java:98)
at org.objectweb.carol.jndi.spi.ContextWrapper.lookup(ContextWrapper.java:112)
at javax.naming.InitialContext.lookup(Unknown Source)
at org.hibernate.transaction.JTATransactionFactory.isTransactionInProgress(JTATransactionFactory.java:83)
Has anyone noticed a similar behavior? Any thoughts on a workaround?
Thanks,
Aaron
Login
FAQ
Search