1 Reply Latest reply on Feb 20, 2013 3:50 AM by Jörg Hoh

    CQ5 Publisher OutofMemory

    Adnan_N

      Hi Folks,

       

      Our production & QA CQ5 instance goes out of memory sometimes and we have to restart it to recover. Thread dump at the time of issue is suggesting that it has something to do with LDAPUserSync, here is somepart of thread dump (most of the threads have this state)

       

       

      "xx.xx.xx.xx [1360856204320] GET /libs/cq/core/content/systemready.txt HTTP/1.1" daemon prio=10 tid=0x0000002b3adf2400 nid=0x6076 waiting for monitor entry [0x0000000046f95000..0x0000000046f97db0]
         java.lang.Thread.State: BLOCKED (on object monitor)
                at com.day.crx.security.ldap.LDAPUserSync$2.call(LDAPUserSync.java:181)
                - waiting to lock <0x0000002a9be162f8> (a java.lang.Class for com.day.crx.security.ldap.LDAPUserSync)
                at com.day.crx.security.ldap.LDAPUserSync.performUpdate(LDAPUserSync.java:226)
                at com.day.crx.security.ldap.LDAPUserSync.syncUser(LDAPUserSync.java:178)
                at com.day.crx.security.ldap.LDAPLoginModule.commit(LDAPLoginModule.java:266)
                at sun.reflect.GeneratedMethodAccessor43.invoke(Unknown Source)
                at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                at java.lang.reflect.Method.invoke(Method.java:597)
                at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
                at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
                at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
                at java.security.AccessController.doPrivileged(Native Method)
                at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
                at javax.security.auth.login.LoginContext.login(LoginContext.java:580)
                at org.apache.jackrabbit.core.security.authentication.JAASAuthContext.login(JAASAuthContext.java:60)
                at org.apache.jackrabbit.core.RepositoryImpl.login(RepositoryImpl.java:1474)
      
      

       

      Has anyone seens sililar issue before? Can it be because of LDAP Server not responding? Any pointers which can help resolve this problem?

       

      Thanks in advance!

        • 1. Re: CQ5 Publisher OutofMemory
          Jörg Hoh Adobe Employee

          If you encounter an out-of-memory situation, a threaddump doesn't help you in the first place. You need an heapdump then. So please configure your JVM settings with the additional parameter "-XX:+HeapDumpOnOutOfMemoryError", and check for any heapdumps written in such situations. It should indicate more exactly, where your problem is.

           

          Jörg