On Mon, Jan 10, 2005 at 05:25:16PM -0500, Net Llama! wrote:
> What happens if you export LD_ASSUME_KERNEL=2.2.5 before running
> your java
> widget?
i've tried that before, and just tried it again. it doesn't help the
problem of the one java thread sucking up max cpu and becoming
nonresponsive.
What happens if you export LD_ASSUME_KERNEL=2.2.5 before running your java
widget?
On Tue, 11 Jan 2005, Peter wrote:
> Your report is with a 1.3 JDK. I'd suggest if you want to use Java, use
> a 1.4.2 JDK. They are pretty solid.
>
> The problem I am getting does not result in any processes cras
Your report is with a 1.3 JDK. I'd suggest if you want to use Java, use
a 1.4.2 JDK. They are pretty solid.
The problem I am getting does not result in any processes crashing. It
just results in maxed out CPU.
Regards, Peter
http://rimuhosting.com
McGroarty wrote:
[Snip much discussion of Ja
Hi. Sorry about not posting the version info.
I'm seeing the problems on various kernels. UML kernels of 2.4.27 and
2.6.9-bb4 (which seems to work very well, btw). Skas kernels of 2.6.8.1
+ skas3-v7.
The host and guest distro I've noticed this on are White Box Enterprise
Linux 3. They repor
[Snip much discussion of Java errors]
I installed Java, curious to see if I would have these same problems.
Curiously, even just running the java command fails about one time in
three. When it fails, it looks like this:
[EMAIL PROTECTED]:~$ cat /proc/version
Linux version 2.4.27-1um ([EMAIL PROTE
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 o
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
> pr
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).
