Ok, thanks for the insights,
On Sun, Nov 19, 2017 at 2:38 PM, Andy Seaborne <[email protected]> wrote: > Hi there, > > If you get a core dump, the JVM has crashed and it's a platform issue. > There isn't anything in Jena that can cause this - it's pure java. All the > event log seems to say is that some parts of Jena were JIT'ed just prior to > the crash. > > Andy > > > On 19/11/17 09:41, Mohammad Noorani Bakerally wrote: > >> I am getting a core dump. It is not always occurring. I am doing a >> performance test on a java application. A python script is executing the >> jar several times and the dump start to occur after the 5th occurence. I >> cannot say for sure if its because of Jena but this is what appears in the >> compilation events: >> >> >> Compilation events (10 events): >> Event: 11,376 Thread 0x00007f2290209000 nmethod 4045 0x00007f2281eb3390 >> code [0x00007f2281eb3500, 0x00007f2281eb3718] >> Event: 11,450 Thread 0x00007f229020c000 4046 4 >> org.apache.jena.sparql.algebra.AlgebraGenerator::<init> (20 bytes) >> Event: 11,454 Thread 0x00007f229020c000 nmethod 4046 0x00007f2281eb2d50 >> code [0x00007f2281eb2ee0, 0x00007f2281eb3188] >> Event: 11,484 Thread 0x00007f229020d800 4047 4 >> org.apache.jena.sparql.engine.QueryExecutionBase::startQueryIterator >> (191 bytes) >> Event: 11,494 Thread 0x00007f2290209000 4048 4 >> java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync::<init> (5 >> bytes) >> Event: 11,494 Thread 0x00007f229020c000 4049 4 >> java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock::<init> (13 >> bytes) >> Event: 11,494 Thread 0x00007f229020c000 nmethod 4049 0x00007f2281eb5890 >> code [0x00007f2281eb59e0, 0x00007f2281eb5a78] >> Event: 11,494 Thread 0x00007f229020c000 4050 4 >> java.util.concurrent.locks.ReentrantReadWriteLock$WriteLock::<init> (13 >> bytes) >> Event: 11,495 Thread 0x00007f229020c000 nmethod 4050 0x00007f2281ec3850 >> code [0x00007f2281ec39a0, 0x00007f2281ec3a38] >> Event: 11,496 Thread 0x00007f2290209000 nmethod 4048 0x00007f2281ec3490 >> code [0x00007f2281ec35e0, 0x00007f2281ec3718] >> >> The entire log can be found in the attached file. Any reason why this is >> occuring ? >> >> thanks >> Noor >> >> >
