Reliable way to handle Java node crashs?

ingo.schramm <>
Tue Jun 29 09:24:08 CEST 2010


BTW, for a certain application I wrote an Erlang/Java app called "ej"
abstracting all that stuff. An Erlang app maintains a Java node,
restarts it etc. Messages are abstracted into one common format with
an API. It's available here: http://github.com/nerlo/nerlo. I plan to
distribute it separately from nerlo once it has been proven(!) to be
rock solid and once it is documented.

Cheers,
Ingo

On Jun 29, 2:09 am, zabrane Mikael <> wrote:
> Trying to restart the same failing test, I got (maybe) a useful info:
>
> beam.smp(89316,0xb14d1000) malloc:
> *** mmap(size=730857472) failed (error code=12)
> *** error: can't allocate region
> *** set a breakpoint in malloc_error_break to debug
>
> Crash dump was written to: erl_crash.dump
> eheap_alloc: Cannot allocate 583848200 bytes of memory (of type "heap").
>
> Abort trap
>
> 2010/6/29 zabrane Mikael <>
>
> > Now, my Java node is restared after each crash !
> > But for one of my message data, I got this strange Erlang error:
>
> > beam.smp(89316,0xb14d1000) malloc:
> > *** mmap(size=730857472) failed (error code=12)
> > *** error: can't allocate region
> > *** set a breakpoint in malloc_error_break to debug
>
> > Could someone tell me what happens to the Erlang VM?
>
> > Regards
> > Zabrane
>
> --
> Regards
> Zabrane


More information about the erlang-questions mailing list