This content has been marked as final. Show 3 replies
Typically that is caused by JNI code.1 person found this helpful
The 64 bit VM itself is more likely to cause that than the 32 bit VM.
Per posts on the JNI forum there are specific vm options which can cause that to occur. So if you are using hotspot/gc options then you should look for those threads.
Thanks for this suggestion, we will try removing gc options altogether to see if it helps.
Edited by: 843727 on 14-Mar-2011 11:57
With this SIGSEGV (Segmentation fault) error we were able to troubleshoot by debugging the code referenced in "Java frames:" subsection under THREAD section.
Therefore looking at Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
Code suggests the exception was thrown while trying to create a new thread, within the org.trippi.io.RIOTripleIterator. The code here was re-factored to use thread pooling instead of creating new threads each time, see here https://jira.duraspace.org/browse/FCREPO-873 for more info. This helped reduced the SIGSEGV errors significantly although not completely.
Edited by: 843727 on 18-Apr-2011 05:00