Closed spagnuolocarmine closed 7 years ago
You should probably look into the call stack and/or run this application through a debugger (and/or enable core dumps) to see exactly where it is failing. From there, you can start trying to figure out why it is failing.
I don't see any mention of MPI in the diagnostic output -- do you know that this issue is caused by Open MPI somehow?
The diagnostic output shows that this is the call stack when it crashed -- you should probably start looking there.
> Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
> V [libjvm.so+0x8cb59c] Monitor::wait(bool, long, bool)+0x35c
> V [libjvm.so+0x4a6d4b] CompileQueue::get()+0x13b
> V [libjvm.so+0x4a8f9b] CompileBroker::compiler_thread_loop()+0x18b
> V [libjvm.so+0xa5cbcf] JavaThread::thread_main_inner()+0xdf
> V [libjvm.so+0xa5ccfc] JavaThread::run()+0x11c
> V [libjvm.so+0x911048] java_start(Thread*)+0x108
> C [libpthread.so.0+0x7aa1] start_thread+0xd1
I'm going to tentatively close this issue because I don't see the relation to MPI in the information that you have provided. If you find further information to indicate that Open MPI is somehow involved in the crash, feel free to re-open the bug (or open a new one). Thanks!
I have installed and configured MPI and Java, but sometimes (really often) my job was killed and enclosed there is the log. Please help me...
Thank you ...