Error Messages | Community
Skip to main content
sumitroy909
Level 2
October 20, 2017
Solved

Error Messages

  • October 20, 2017
  • 4 replies
  • 2643 views

Hi can anyone please tell Why I am getting this errors in my logs

17.10.2017 12:23:41.120 *ERROR* [qtp1447577037-166] org.apache.felix.metatype Missing element AD in element OCD : bundle://22.0:0/OSGI-INF/metatype/org.apache.jackrabbit.oak.blob.cloud.s3.S3DataStoreService.xml

17.10.2017 12:23:41.122 *ERROR* [qtp1447577037-166] org.apache.felix.metatype Missing element AD in element OCD : bundle://22.0:0/OSGI-INF/metatype/org.apache.jackrabbit.oak.blob.cloud.s3.SharedS3DataStoreService.xml

17.10.2017 12:23:41.294 *ERROR* [CM Event Dispatcher (Fire ConfigurationEvent: pid=org.apache.sling.event.jobs.QueueConfiguration)] org.apache.sling.event [org.apache.sling.event.jobs.QueueConfiguration] singleton pid org.apache.sling.event.jobs.QueueConfiguration supplied, but matches an existing factory pid at index: 0

17.10.2017 12:23:41.298 *ERROR* [CM Event Dispatcher (Fire ConfigurationEvent: pid=org.apache.sling.event.jobs.QueueConfiguration)] org.apache.felix.configadmin Service [org.apache.felix.cm.ConfigurationAdmin,27, [org.osgi.service.cm.ConfigurationAdmin]] Unexpected problem delivering configuration event to [org.osgi.service.cm.ConfigurationListener, id=46, bundle=17/slinginstall:org.apache.felix.configadmin-1.9.0-B002.jar] (java.lang.IllegalStateException: Singleton pid supplied matching a previous factory pid org.apache.sling.event.jobs.QueueConfiguration)

17.10.2017 12:26:43.131 *ERROR* [Thread-279] com.day.cq.dam.core.impl.ui.preview.FolderPreviewUpdaterImpl error while committing changes: /content/dam/baseload-mixed-50MBavg/top8/second1/top8second1FileNum3.jpg

17.10.2017 21:46:13.672 *ERROR* [qtp1447577037-10208] org.apache.felix.metatype Missing element AD in element OCD : bundle://22.0:0/OSGI-INF/metatype/org.apache.jackrabbit.oak.blob.cloud.s3.S3DataStoreService.xml

17.10.2017 21:46:13.672 *ERROR* [qtp1447577037-10208] org.apache.felix.metatype Missing element AD in element OCD : bundle://22.0:0/OSGI-INF/metatype/org.apache.jackrabbit.oak.blob.cloud.s3.SharedS3DataStoreService.xml

17.10.2017 21:46:14.536 *ERROR* [CM Event Dispatcher (Fire ConfigurationEvent: pid=org.apache.sling.event.jobs.QueueConfiguration)] org.apache.sling.event [org.apache.sling.event.jobs.QueueConfiguration] singleton pid org.apache.sling.event.jobs.QueueConfiguration supplied, but matches an existing factory pid at index: 0

17.10.2017 21:46:14.537 *ERROR* [CM Event Dispatcher (Fire ConfigurationEvent: pid=org.apache.sling.event.jobs.QueueConfiguration)] org.apache.felix.configadmin Service [org.apache.felix.cm.ConfigurationAdmin,27, [org.osgi.service.cm.ConfigurationAdmin]] Unexpected problem delivering configuration event to [org.osgi.service.cm.ConfigurationListener, id=46, bundle=17/slinginstall:org.apache.felix.configadmin-1.9.0-B002.jar] (java.lang.IllegalStateException: Singleton pid supplied matching a previous factory pid org.apache.sling.event.jobs.QueueConfiguration)

aem version -6.3GA

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by edubey

There are many out there but these should help you to get started

Storage Elements in AEM 6.3

Data Store Configurations

AEM with MongoDB

Configuring node stores and data stores in AEM 6

4 replies

smacdonald2008
Level 10
October 20, 2017

YOu need to provide more information. Do these messages show up when you deployed an OSGi bundle? DId they all of a sudden show up or have always been there.

Looks like there is a issue with configuration.

sumitroy909
Level 2
October 24, 2017

Actually, I was trying to start AEM 6.3GA with the previous version of S3 connectors, when I started the AEM these messages showed up in the logs.Can you please provide me with some doc's link, from were I can learn more about AEM and its different setups like tar+s3,mongo+s3,fds etc

edubey
edubeyAccepted solution
Level 10
October 24, 2017
sumitroy909
Level 2
October 24, 2017

Thanks a lot!