2908590 - "Change log currently locked" while performing a maintenance on SLD CR Content.

While performing SLD namespace maintenance like adding or removing it from SLD GUI, it raises following error afterwards. (Even though not being logged onto namespace you are trying to perform the change)

"com.sap.tc.webdynpro.services.exceptions.WDNonFatalException: CIM_ERR_FAILED: (XXXXXXXX) Change log currently locked"



Then going further, you notice the following also from SLD logs ("Administration" -> "Log")

##########
#xxx xx/xx/xxxx xx:xx:xx.957 [HTTP Worker [@xxxxxxxxx]] ERROR com.sap.sld.wd.businesssystem.BusinessSystemDetailView: Problem accessing CIM
Thrown: 
com.sap.cim.lib.core.CIMLockException: CIM_ERR_FAILED: (XXXXXXXXXX) Change log currently locked
at com.sap.cim.lib.objmgr.core.CIMLocking.enhanceLockCollision(CIMLocking.java:308)
at com.sap.cim.lib.objmgr.core.CIMLocking.lockChangeLog(CIMLockin
...
...
Caused by: com.sap.engine.frame.core.locking.LockException: Cannot lock [XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX...............xxxxxxxxx, CIM:S:global, ChangeLog, X]; it is in use by another owner. The lock collision occurred with user J2EE_GUEST.
at com.sap.engine.core.locking.impl3.LockingManagerImpl.lockInternal(LockingManagerImpl.java:168)
at com.sap.engine.core.locking.AbstractLockingManagerImpl.lock(AbstractLockingManagerImpl.java:466)
at com.sap.engine.services.applocking.AbstractBaseLocking.lockInternal(AbstractBaseLocking.java:152)
##########

The same above is also perceived on DefaultTrace logs.

• System Landscape Directory
• SAP Netweaver Version Independent

lock, namespace, temp, sld/import/temp0, exceptions, com.sap.tc.webdynpro.services.exceptions.WDNonFatalException, CIM_ERR_FAILED, CNBSCSAPSOL3, remove, add, import, export, locked , KBA , BC-CCM-SLD , System Landscape Directory / Component Repository , BC-CCM-SLD-JAV , System Landscape Directory Java Client & Server , Problem