Deadlock is not going to produce 100% cpu usage, and I see no class loading going on in this dump. The JNDIView is recursing resolving child contexts and is 519 deep. I doubt you actually have that nested a namespace so there must be a cycle in the JNDI tree that is causing the looping.
-- xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx
Chris Bonham wrote:
I'm running JBoss 3.2.2 final on Windows XP Pro SP1, Sun JDK 1.4.1_04. When I try to call the list method on JNDIView through jmx-console, the application jumps to ~500MB memory and 100% CPU. I've included the full thread dump; there appears to be a deadlock loading a class at JNDIView.java:307. Any ideas?
Thanks.
-- Chris Bonham President/CEO Third Eye Consulting, Inc. [EMAIL PROTECTED] http://www.thirdeyeconsulting.com 317.823.3686 317.823.0353 (FAX)
------------------------------------------------------- This SF.Net email sponsored by: ApacheCon 2003, 16-19 November in Las Vegas. Learn firsthand the latest developments in Apache, PHP, Perl, XML, Java, MySQL, WebDAV, and more! http://www.apachecon.com/ _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
