On Mon, Jan 10, 2005 at 05:33:30PM +1300, 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.
i see the exact same problem with another uml provider (not rimu). they're running 2.4.26-2um. i'm running debian unstable on it. my jboss 4 or 3 instances exhibit this same behavior when i run them in jdk1.5. starting the jvm with -Xint alleviates the problem, but i'm pretty sure it's making the whole app run slower. experimenting locally with the 2.4.26-3um-1 kernel that debian packages, my entire machine locks and i need to kill the whole linux process. i don't know how to fix or debug it, either. if anyone has any ideas, i'd be happy to try them. -- John M Flinchbaugh [EMAIL PROTECTED]
signature.asc
Description: Digital signature
