diablo 1.5 died after 5 day uptime
vadimnuclight at tpu.ru
Fri May 26 08:41:55 PDT 2006
26.05.06 @ 20:32 Kurt Miller wrote:
>> >> I have an SMP (HTT) machine with 5.5-PRERELEASE, using official >>
>> diablo 1.5 jdk
>> >> binaries from beginning of April. As suggested, I now run java with
>> >> -XX:+UseMembar cmdline switch, that resolved problem with crashing
>> >> application after startup.
>> >> But today after 5 days uptime now-debugged-and-set-to-long-run server
>> >> process
>> >> have crashed, with 100M coredump file. What happened? Below are log
>> >> gdb backtrace.
>> >> As some additional info: I have limits in login.conf, 32M for
>> >> size
>> >> and 256M for virtual mem size; yesterday when I looked at process
>> >> it was about 10M resident and 250M virtual - could be a reason?..
>> > Hi,
>> > It does appear that you've run out of vm.
>> > <snip>
>> >> #21 0x0a3fceda in vm_exit_out_of_memory ()
>> >> from /usr/local/diablo-jdk1.5.0/jre/lib/i386/client/libjvm.so
>> But so why it dies on signal 11 with scary logs and coredump, instead of
>> descriptive out-of-memory diagnostics and graceful shutdown? Isn't that
>> a bug ?
>> 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 ?
WBR, Vadim Goncharov
More information about the freebsd-java