Re: Java crashes - only message is "Aborted"???
dduck wrote:
On Jun 27, 6:07 pm, Nigel Wade <n...@ion.le.ac.uk> wrote:
dduck wrote:
On Jun 27, 3:54 pm, Gordon Beaton <n...@for.email> wrote:
Try doing "ulimit -c unlimited" in the shell (or start script) before
starting the application, or confirm with "ulimit -c" that the setting
is "unlimited". That should get you a corefile.
Thank you. We will try that.
Sincerely,
Anders
What OS are you running this on?
You might be hitting a resource limit which is aborting the command. What
limits
are imposed (CPU, stack size, vm size etc) in your environment?
We are running on RedHat Linux on an x86 arch. I will post precise
info on this tomorrow when I get back to the office (no remote access
to that particular machine).
We constantly monitor the app with JConsole. There are no indications
that any obvious resource is being exhausted (CPU, memory, threads,
classes loaded...).
Thank you for your suggestions - I will look into it and report the
findings.
Sincerely,
Anders
You won't get any indication that a resource limit is nearly exhausted, your
program only receives the indication when it is exhausted. That may just be a
failure to allocate a new resource, such as failing to open a file because you
already have open the max. allowed, or the program being aborted due to
exceeding the CPU limit.
"ulimit -a" should tell you your limits in Linux.
--
Nigel Wade, System Administrator, Space Plasma Physics Group,
University of Leicester, Leicester, LE1 7RH, UK
E-mail : nmw@ion.le.ac.uk
Phone : +44 (0)116 2523548, Fax : +44 (0)116 2523555