Prev: ECLIPSE - slow deployment with WAS 6.0
Next: Using browser's proxy-settings from a javaws-app?
From: jolz on 30 Jan 2010 15:03
> So why on 32bit system there will not be thrown exception java heap
> space if there is memory leak instead of SIGSEGV?

Sun's JVM will throw OutOfMemoryError if memory limit for java was hit
but will crash if memory limit for the process will be reached. On 64
bit system it's hard to reach that limit (unless the disc is full and
there's no place for swap), but on 32 bit system native code may have
very little memory to use (for example yours 1024m (-Xmx) + 512m
(-XX:MaxPermSize) + memory for used by JVM will leave very little from
2G (depends on the OS) available for a process). If memory leaks all
available memory will be used very soon.
From: Sherkan on 30 Jan 2010 16:35
OK,
2 days ago I've started server and it worked for about 1,5 day....10
minutes ago I had to change something application, after reboot my
server worked for 4 minutes!
Why server crash after 4 minutes of work?
From: Lew on 30 Jan 2010 17:28
Sherkan wrote:
> 2 days ago I've started server and it worked for about 1,5 day....10
> minutes ago I had to change something application, after reboot my
> server worked for 4 minutes!
> Why server crash after 4 minutes of work?

Because the conditions that cause the crash manifested after four minutes.

I'd be more specific, but my crystal ball is in the shop.

--
Lew
From: Arne Vajhøj on 30 Jan 2010 22:55
On 28-01-2010 07:40, Roedy Green wrote:
> What is centos? Who the made the JVM?

May I suggest there two wonderful services:

http://www.google.com/
http://www.wikipedia.org/

They are absolutely excellent to answer that type
of questions.

Arne


From: Kevin McMurtrie on 31 Jan 2010 01:18
In article <hk21og$hsk$1(a)news.interia.pl>,
jolz <BardzoTajneKonto(a)interia.pl> wrote:

> > So why on 32bit system there will not be thrown exception java heap
> > space if there is memory leak instead of SIGSEGV?
>
> Sun's JVM will throw OutOfMemoryError if memory limit for java was hit
> but will crash if memory limit for the process will be reached. On 64
> bit system it's hard to reach that limit (unless the disc is full and
> there's no place for swap), but on 32 bit system native code may have
> very little memory to use (for example yours 1024m (-Xmx) + 512m
> (-XX:MaxPermSize) + memory for used by JVM will leave very little from
> 2G (depends on the OS) available for a process). If memory leaks all
> available memory will be used very soon.

I don't know about CentOS, but many OSes log malloc/free errors. It
helps debug a problem that may have deferred symptoms.
--
I won't see Google Groups replies because I must filter them as spam
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4
Prev: ECLIPSE - slow deployment with WAS 6.0
Next: Using browser's proxy-settings from a javaws-app?