We are running Sun JDK 1.4.2_05 on RHEL 3. The Tomcat is 5.0 something
(I'm out of tow at the moment so I don't have access to the info).
Frankly, I'm suspecting that ehcache is returning a bad document to
Castor although I don't have any proof. But if that is the case I
really would have expected Castor to get or throw an exception, not just
call the classloader over and over.
The lock at 0x60b19148 was held by the last thread which was
"http-8080-Processor26" daemon prio=1 tid=0x0821b148 nid=0x1e8b waiting
for monitor entry [2cafd000..2caff87c]
at java.lang.String.replace(String.java:1555)
at java.net.URLClassLoader$1.run(URLClassLoader.java:190)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
- locked <0x60b1d920> (a sun.misc.Launcher$ExtClassLoader)
at java.lang.ClassLoader.loadClass(ClassLoader.java:282)
- locked <0x60b19148> (a sun.misc.Launcher$AppClassLoader)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274)
- locked <0x60b19148> (a sun.misc.Launcher$AppClassLoader)
Ralph
Pier Fumagalli wrote:
On 22 Dec 2005, at 18:16, Ralph Goers wrote:
We finally got some thread dumps from our production server. It
shows something very different than what we were seeing in testing.
First, this happens under light load after running for days. To
summarize, many threads are waiting for the ResourceLimitingPool and
several are waiting for the class loader. This system hasn't had the
pools tuned so I'm not surprised about pool contention, but I don't
believe that is the issue. That is because the thread holding the
lock is simply waiting for the class loader.
We took two traces and both were similar, but not identical.
Different threads were holding the class loader lock in both.
However, in both cases the threads holding the class loader lock
were called from Castor while creating the portal layout.
So far, we have been speculating that the problem is due to a
problem with the NPTL threads on Enterprise Linux 3. However, I'm
wondering if perhaps castor is having problems and simply calling
the class loader over and over.
I'd appreciate any ideas.
Ok, as far as I can see down the dumps you might have some problems
with Catalina's classloader implementation locking up at 0x60b19148:
at org.apache.catalina.loader.WebappClassLoader.loadClass
(WebappClassLoader.java:1255)
That seems odd though... I thought that code was debugged pretty
thoroughly, unless, a seconday lock at 0x60cd9970 prevents the first
one to be released...
Anyhow, from my experience, NPTL don't cause any whatsoever problem
under Linux, but that said, I'm running on Jetty 4 with BEA JRockit
1.4.2. What VM and what container are you actually using?
Pier
