Getting error if i point to same repository of blob from different instance

[JeganNa]

The repository which i am trying to point is Azure blob and if i point the same repository for two different instance. the second instance is not able to acquire a lease. and it is not coming up because of this issue. 

In error log i noticed two issue
1.  javax.management.InstanceAlreadyExistsException: org.apache.jackrabbit.oak:name=BlobStore-MemCache,type=CacheStats

at java.management/com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:323)

2. org.apache.felix.log.LogException: java.io.IOException: java.io.IOException: There is currently a lease on the blob and no lease ID was specified in the request. Please see the cause for further information.

    at org.apache.jackrabbit.oak.segment.azure.AzureRepositoryLock.lock(AzureRepositoryLock.java:117) [org.apache.jackrabbit.oak-segment-azure:1.64.0]

    at org.apache.jackrabbit.oak.segment.azure.AzurePersistence.lockRepository(AzurePersistence.java:107) [org.apache.jackrabbit.oak-segment-azure:1.64.0]

    at org.apache.jackrabbit.oak.segment.file.FileStore.<init>(FileStore.java:144) [org.apache.jackrabbit.oak-segment-tar:1.64.0]

    at org.apache.jackrabbit.oak.segment.file.FileStoreBuilder.build(FileStoreBuilder.java:445)

[Jörg_Hoh]

May I ask what version of AEM you are using? It's not AEM 6.5 and it's not AEM CS...

[JeganNa]

Yeah I am using aem 6.5. Any issues with that ? 

[Jörg_Hoh]

Sorry, my bad. Forgot that the latest AEM 6.5 SP updated Oak to a very recent version as well, and was a bit confused

Seems like https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/installing-aem-6-5-with-s3... is pretty much the same problem, but your situation is different (you seem to have cloned an already running instance, and S3 vs Azure).

Sorry, my experience with these setups is quite limited