On Monday 10 January 2005 05:33, Peter wrote: > I have some users running 1.5 Java VMs. They run for a bit. Then seem > to get 'locked up'. > > The process maxes out the UML CPU. They do not respond to a kill -3 > (which normally causes a Java stack trace to be output). The process > does not output anything when I strace it (after it locks up). > > This happens when the 1.5 JDK is used to start Tomcat. And it has > happened running other Java apps as well. I don't see the problem with > any non-Java apps. The problem also happens with the Update 1 release > of the 1.5 JDK. > > I never see the problem with the 'old' 1.4.* releases. I don't see any > reports like this with JDK 1.5 users on non-UML systems. > > So I'm guessing there is a UML/JD1.5 interaction issue here somewhere. > > Is anyone else seeing this issue? And can someone give me an idea of > how to collect more information about this problem. Oh, and wild > guesses at the cause of the problem are also invited :) First post the host/guest kernel and glibc version, at least... running strace on the Java process may give more info.
Also, try running different UML releases, as 2.6.9-bb4. -- Paolo Giarrusso, aka Blaisorblade Linux registered user n. 292729 http://www.user-mode-linux.org/~blaisorblade ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ User-mode-linux-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/user-mode-linux-user
