0 Replies Latest reply on Dec 6, 2012 12:21 PM by Abdul_Rasheed

    Cluster Controller exception during DR scenario

    Abdul_Rasheed

      Hi All,

       

      We have setup a new DR environment as mentioned below. While replicating a DR scenario we found issues with the DR Author.

       

      • Set three author Instances (Primary , secondary and DR) and one publish instance. <All 3 are on a separate windows machine>
      • Changed the content in DR, it was reflected to the other 2 clustered author Instances and vice-versa. <Cluster works fine>
      • <DR Scenario> Unplugged the Primary and secondary Instance LAN cables.
      • Changed the content in DR server and tried to replicate , which resulted in an exception.
      • Restarted the DR Instance. It was working fine and was a stand alone cluster.

       

      Error log while we did step 4.

       

      06.12.2012 00:01:07.261 *ERROR* [0:0:0:0:0:0:0:1 [1354732267246] POST /content/xxx/xxx/jcr:content/par/text_5048 HTTP/1.1] org.apache.sling.servlets.post.impl.operations.ModifyOperation Exception during response processing. java.lang.IllegalStateException: d

      at com.day.crx.core.cluster.ClusterController.checkNotStopped(ClusterController.java:1384)

      at com.day.crx.core.cluster.ClusterController.newCall(ClusterController.java:887)

      at com.day.crx.persistence.tar.ClusterTarSet.call(ClusterTarSet.java:1172)

      at com.day.crx.persistence.tar.ClusterTarSet.lockSend(ClusterTarSet.java:758)

      at com.day.crx.persistence.tar.ClusterTarSet.lockShared(ClusterTarSet.java:655)

      at com.day.crx.persistence.tar.ClusterTarSet.lockShared(ClusterTarSet.java:614)

      at com.day.crx.persistence.tar.ClusterTarSet.lockShared(ClusterTarSet.java:642)

      at com.day.crx.persistence.tar.ClusterTarSet.lockShared(ClusterTarSet.java:614)

      at com.day.crx.persistence.tar.TarPersistenceManager.tryStore(TarPersistenceManager.java:525 )

      at com.day.crx.persistence.tar.TarPersistenceManager.storeTransaction(TarPersistenceManager. java:500)

      at com.day.crx.persistence.tar.TarPersistenceManager.store(TarPersistenceManager.java:488)

      at org.apache.jackrabbit.core.state.SharedItemStateManager$Update.end(SharedItemStateManager .java:757)

      at org.apache.jackrabbit.core.state.SharedItemStateManager.update(SharedItemStateManager.jav a:1487)

      at org.apache.jackrabbit.core.state.LocalItemStateManager.update(LocalItemStateManager.java: 351)

      at org.apache.jackrabbit.core.state.XAItemStateManager.update(XAItemStateManager.java:354)

      at org.apache.jackrabbit.core.state.LocalItemStateManager.update(LocalItemStateManager.java: 326)

       

      Is this a known issue with CQ?

       

      CQ Version used is 5.4

       

      Appreciate your inputs on this.

       

      Thanks,

      Abdul