"oracle.mds.core.ConcurrentMOChangeException: MDS-00165" Exception While Deploying an Application

(Doc ID 1495871.1)

Last updated on NOVEMBER 18, 2016

Applies to:

Oracle WebCenter Portal - Version 11.1.1.6.0 and later
Information in this document applies to any platform.

Symptoms

In a four-node cluster with Managed Servers created with the CustomPortal template. There are 2 managed servers running on each machine.
The 6.5.1 Configuring a Cluster for WebCenter Portal Applications documentation has been followed to create the managed servers.


When deploying application to the cluster (even the starter WebCenter Portal application) then randomly the following exception warning may get logged in the out file of one or more nodes of the cluster:

<Warning> <oracle.webcenter.lifecycle.listener.LifecycleServletContextListener> <BEA-000000> <
oracle.webcenter.lifecycle.LifecycleException: MDSException while creating an export set import lock
        at oracle.webcenter.lifecycle.operation.LockUnit.doImportExportSet(LockUnit.java:359)
        at oracle.webcenter.lifecycle.operation.ImportExportSetOperation.doImportExportSet(ImportExportSetOperation.java:106)
        at oracle.webcenter.lifecycle.LifecycleService.doImportExportSet(LifecycleService.java:585)
...
        at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
        at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused By: oracle.mds.core.ConcurrentMOChangeException: MDS-00165: metadata Object "/oracle/webcenter/lock/exportsetImport/exportsetImport.xml" has changed
MDS-00516: failure to create document /oracle/webcenter/lock/exportsetImport/exportsetImport.xml because it already exists in the metadata repository
        at oracle.mds.core.UpdateableMOContent.constructConcurrentMOChangeException(UpdateableMOContent.java:1376)
        at oracle.mds.core.UpdateableMOContent.saveMOContent(UpdateableMOContent.java:1143)
        at oracle.mds.core.MDSTransaction.flushChangesToPTrans(MDSTransaction.java:851)
        at oracle.mds.core.MDSTransaction.internalCommit(MDSTransaction.java:2928)
        at oracle.mds.core.MDSSession.flushChanges(MDSSession.java:1022)
...
        at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
        at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused By: oracle.mds.persistence.DocumentExistsException: MDS-00516: failure to create document /oracle/webcenter/lock/exportsetImport/exportsetImport.xml because it already exists in the metadata repository
        at oracle.mds.internal.persistence.db.BaseDBMSConnection.createDocWithComment(BaseDBMSConnection.java:979)
        at oracle.mds.internal.persistence.db.BaseDBMSConnection.createStoreDocument(BaseDBMSConnection.java:796)
        at oracle.mds.persistence.DelegatingMetadataStoreConnection.createStoreDocument(DelegatingMetadataStoreConnection.java:302)
        at oracle.mds.internal.persistence.BufferedMSConnection.createStoreDocument(BufferedMSConnection.java:321)
...
        at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
        at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
        at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
        at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

  

 


Steps to Reproduce:

  1. Create a 4-node cluster with 2 machines, where both machine hosts 2 managed server. Create the Managed Servers with the CustomPortal template using the following documentation:
    6.5.1 Configuring a Cluster for WebCenter Portal Applications
  2. Create a starter WebCenter Portal application in JDeveloper.
  3. Deploy the application to the cluster.
  4. Check the out file of the nodes and notice the exception.

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms