222 words

Crash due to memory problems

#1
2016-11-14 06:42

We had a crash of our system, log reports the following:

...

[2016-11-10 08:28:14 #11 server]
java.lang.OutOfMemoryError: GC overhead limit exceeded
at com.objectdb.o.PLN.Vm(PLN.java:495)
at com.objectdb.o.TAI.A(TAI.java:201)
at com.objectdb.o.TAI.UI(TAI.java:134)
at com.objectdb.o.TQI.UI(TQI.java:54)
at com.objectdb.o.TQI.UI(TQI.java:54)
at com.objectdb.o.MQI.VM(MQI.java:140)
at com.objectdb.o.MQI.VM(MQI.java:120)
at com.objectdb.o.MQI.VM(MQI.java:120)
at com.objectdb.o.MQI.VM(MQI.java:120)
at com.objectdb.o.MQI.VM(MQI.java:120)
at com.objectdb.o.MQI.VM(MQI.java:120)
at com.objectdb.o.MQI.VM(MQI.java:120)
at com.objectdb.o.XQI.VM(XQI.java:67)
at com.objectdb.o.XQI.VM(XQI.java:67)
at com.objectdb.o.GQI.UI(GQI.java:148)
at com.objectdb.o.PRG.ag(PRG.java:687)
at com.objectdb.o.PRG.af(PRG.java:555)
at com.objectdb.o.QRM.Vo(QRM.java:286)
at com.objectdb.o.MST.Vo(MST.java:988)
at com.objectdb.o.STC.s(STC.java:464)
at com.objectdb.o.SHN.aj(SHN.java:489)
at com.objectdb.o.SHN.K(SHN.java:155)
at com.objectdb.o.HND.run(HND.java:133)
at java.lang.Thread.run(Unknown Source)

[2016-11-10 09:48:41 #12 store]
SectionClassifier: SectionClassifier{0->merger[2075]-missing:1}

[2016-11-10 09:48:41 #13 *]
[ObjectDB 2.6.7_05] Unexpected exception (Error 990)
  Generated by Java HotSpot(TM) 64-Bit Server VM 1.8.0_91 (on Windows Server 2012 R2 6.3).
Please report this error on http://www.objectdb.com/database/issue/new
com.objectdb.o.InternalException: java.lang.OutOfMemoryError: GC overhead limit exceeded
java.lang.OutOfMemoryError: GC overhead limit exceeded

[2016-11-10 09:57:33 #14 *]
[ObjectDB 2.6.7_05] Unexpected exception (Error 990)
  Generated by Java HotSpot(TM) 64-Bit Server VM 1.8.0_91 (on Windows Server 2012 R2 6.3).
Please report this error on http://www.objectdb.com/database/issue/new
com.objectdb.o.InternalException: java.lang.OutOfMemoryError: GC overhead limit exceeded
java.lang.OutOfMemoryError: GC overhead limit exceeded

[2016-11-10 11:18:38 #15 server]
java.lang.OutOfMemoryError: GC overhead limit exceeded

[2016-11-10 11:18:55 #16 server]
Server on port 3333 has stopped by 5808@wzbhb101

 

hgzwicker
hgzwicker's picture
Joined on 2014-04-09
User Post #22
#2
2016-11-14 07:44

Unlike other exceptions, on OutOfMemoryError the stack trace is not necessarily related to the cause (as the exception can be thrown on any memory allocation that is done when the heap is full). A heap dump may be more helpful.

Usually the solution is to increase the JVM heap size (if possible) or tune the ObjectDB configuration.

If ObjectDB recovery is enabled then ObjectDB should recover automatically when it is restarted. Please check the database with the ObjectDB Doctor to detect errors in the database file.

ObjectDB Support
ObjectDB - Fast Object Database for Java (JPA/JDO)
support
support's picture
Joined on 2010-05-03
User Post #2,637

Post Reply

Please read carefully the posting instructions - before posting to the ObjectDB website.

  • You may have to disable pop up blocking in order to use the toolbar (e.g. in Chrome).
  • Use ctrl + right click to open the browser context menu in the editing area (e.g. for using a browser spell checker).
  • To insert formatted lines (e.g. Java code, stack trace) - select a style in the toolbar and then insert the text in the new created block.
  • Avoid overflow of published source code examples by breaking long lines.
  • You may mark in paragraph code words (e.g. class names) with the code style (can be applied by ctrl + D).
  • Long stack traces (> 50 lines) and complex source examples (> 100 lines) should be posted as attachments.
Attachments:
Maximum file size: 32 MB
Cancel