SAP Knowledge Base Article - Preview

2735469 - AS Java OutOfMemoryError - exit code [666] - Deadlock in error queue

Symptom

AS Java instance restarts due to OutOfMemoryError.

  • dev_server log file shows the following error:
      
    [...]
    F  [Thr 01] F  [Thr 01] *** LOG => Timer expired (120000 ms).
    [...]
    F  *** ERROR => Shutdown timer expired.
    [...]
    F  [Thr 01] *** LOG => exiting (exitcode 22001, retcode 1).
    I  [Thr 01] *** ERROR => e=22 semop(1090519096,(0,-1,4096),1) (22: Invalid argument) [semux0_mt.c  559]
    M  [Thr 01] *** ERROR => CCMS ProcDeregister: lock error [alxxcore_mt. 1845]
    [...]
  • std_server log file shows similar entries referring to "error queue":
      
    [...]
    Server process shutting down with exit code [666]; memory allocation error [OutOfMemoryError]java.lang.OutOfMemoryError: Java heap space (failed to allocate 88 bytes)

     at java.lang.String.intern(Native Method)
     at java.util.jar.Attributes$Name.<init>(Attributes.java:491)
     at java.util.jar.Attributes.putValue(Attributes.java:151)
     at java.util.jar.Attributes.read(Attributes.java:427)
     at java.util.jar.Manifest.read(Manifest.java:200)
     at java.util.jar.Manifest.<init>(Manifest.java:68)
     at java.util.jar.JarFile.getManifestFromReference(JarFile.java:177)
     at java.util.jar.JarFile.getManifest(JarFile.java:154)
     at sun.misc.URLClassPath$JarLoader$2.getManifest(URLClassPath.java:712)
     at java.net.URLClassLoader.defineClass(URLClassLoader.java:281)
     at java.net.URLClassLoader.access$000(URLClassLoader.java:59)
     at java.net.URLClassLoader$1.run(URLClassLoader.java:250)
     at java.security.AccessController.doPrivileged(Native Method)
     at java.net.URLClassLoader.findClass(URLClassLoader.java:243)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:372)
     at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:344)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:313)
     at com.sap.jvm.impl.monitor.vm.ErrorQueue$ErrorQueueDelegateImpl.reallyPoll(ErrorQueue.java:55)
     at com.sap.jvm.impl.monitor.vm.ErrorQueue$ErrorQueueDelegateImpl.remove(ErrorQueue.java:104)
     at com.sap.jvm.monitor.vm.ErrorQueue.remove(ErrorQueue.java:112)
     at com.sap.jvm.monitor.vm.ErrorQueue.remove(ErrorQueue.java:123)
     at com.sap.engine.core.thread.impl3.ErrorQueueHandler.run(ErrorQueueHandler.java:75)
    [...]


Read more...

Environment

  • SAP NetWeaver Application Server Java 7.2/7.3/7.31/7.4
  • SAP Java Virtual Machine (JVM) 6.1

Product

SAP NetWeaver 7.2 ; SAP NetWeaver 7.4 ; SAP NetWeaver 7.5 ; SAP enhancement package 1 for SAP NetWeaver 7.3

Keywords

ErrorQueue.remove, ErrorQueueHandler, com.sap.jvm.impl.monitor.vm, exit code 666, exit code [666], OutOfMemoryError, failed to allocate, Timer expired, Shutdown timer expired, CCMS ProcDeregister, lock error, SAP JVM, SAP Java Virtual Machine , KBA , BC-JVM , SAP Java Virtual Machine , BC-JAS-COR , Enterprise Runtime, Core J2EE Framework , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.