diablo 1.5 died after 5 day uptime

[Vadim Goncharov]

27.05.06 @ 00:07 Kurt Miller wrote:

>> >> From what I can gather from the stack trace, the jvm was
>> > in the process of a graceful shutdown but there wasn't enough
>> > memory for it to pull it off. There is only so much you can
>> > do to protect against out-of-memory errors when you need more
>> > to report it nicely to the user.
>>
>> Hmm, OK. Is there any way to tell Java that memory is about to end
>> before killing ? Or may be a way to make GC to free some memory
>> periodically? May be outside from java, undocumeted external
>> signaling to diablo-jdk ? At last, does it respect login.conf limits
>> at all, doing graceful shutdown before / trying to raise to hard limit ?
>>
>
> If your goal is to limit the amount of memory the jvm uses,
> I would recommend using the standard command line arguments
> that control the heap size (-Xmx & -Xms) and leave your limits

How can I check default values of these on my system ?

> high. Note that the jvm uses more memory then is controlled
> by the -Xmx arg. You need to leave some head room for that if
> your going to be setting your limits lower.

OK, thanx. Is that overhead big?

-- 
WBR, Vadim Goncharov