Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

Problem with cq start up on installation of SP3 on AEM 6.3

Avatar

Level 3

Recently we installed SP3 on AEM 6.3 after installation it's all working and restart also worked good...but when we do deployment in Higher environment after installation of sp3 it is getting failed and start up is not happening after that , as we are seeing bundle errors as below.What could be the reason can someone help please...

*ERROR* [FelixStartLevel] ERROR: Bundle '147' Error starting launchpad:resources/install/30/org.apache.sling.startupfilter.disabler-0.0.1-Rev1758544.jar (org.osgi.framework.BundleException: Unable to resolve org.apache.sling.startupfilter.disabler [147](R 147.0): missing requirement [org.apache.sling.startupfilter.disabler [147](R 147.0)] osgi.wiring.package; (&(osgi.wiring.package=org.apache.sling.startupfilter)(version>=1.0.0)(!(version>=2.0.0))) [caused by: Unable to resolve org.apache.sling.startupfilter [53](R 53.0): missing requirement [org.apache.sling.startupfilter [53](R 53.0)] osgi.implementation; (&(osgi.implementation=osgi.http)(version=1.0)) [caused by: Unable to resolve org.apache.felix.http.jetty [40](R 40.1): missing requirement [org.apache.felix.http.jetty [40](R 40.1)] osgi.wiring.package; (&(osgi.wiring.package=org.osgi.service.log)(version>=1.3.0)(!(version>=2.0.0))) [caused by: Unable to resolve org.apache.sling.commons.logservice [11](R 11.0): missing requirement [org.apache.sling.commons.logservice [11](R11.0)] osgi.wiring.package; (&(osgi.wiring.package=org.slf4j)(version>=1.5.0)(!(version>=2.0.0))) [caused by: Unable to resolve slf4j.api [2](R 2.0): missing requirement [slf4j.api [2](R 2.0)] osgi.wiring.package; (&(osgi.wiring.package=org.slf4j.impl)(version>=1.6.0))]]]]Unresolved requirements: [[org.apache.sling.startupfilter.disabler [147](R 147.0)] osgi.wiring.package; (&(osgi.wiring.package=org.apache.sling.startupfilter)(version>=1.0.0)(!(version>=2.0.0)))])
org.osgi.framework.BundleException: Unable to resolve org.apache.sling.startupfilter.disabler [147](R 147.0): missing requirement [org.apache.sling.startupfilter.disabler [147](R 147.0)] osgi.wiring.package; (&(osgi.wiring.package=org.apache.sling.startupfilter)(version>=1.0.0)(!(version>=2.0.0))) [caused by: Unable to resolve org.apache.sling.startupfilter [53](R 53.0): missing requirement [org.apache.sling.startupfilter [53](R 53.0)] osgi.implementation; (&(osgi.implementation=osgi.http)(version=1.0)) [caused by: Unable to resolve org.apache.felix.http.jetty [40](R 40.1): missing requirement [org.apache.felix.http.jetty [40](R 40.1)] osgi.wiring.package; (&(osgi.wiring.package=org.osgi.service.log)(version>=1.3.0)(!(version>=2.0.0))) [caused by: Unable to resolve org.apache.sling.commons.logservice [11](R 11.0): missing requirement [org.apache.sling.commons.logservice [11](R 11.0)] osgi.wiring.package; (&(osgi.wiring.package=org.slf4j)(version>=1.5.0)(!(version>=2.0.0))) [caused by: Unable to resolve slf4j.api [2](R 2.0): missing requirement [slf4j.api [2](R 2.0)] osgi.wiring.package; (&(osgi.wiring.package=org.slf4j.impl)(version>=1.6.0))]]]] Unresolved requirements: [[org.apache.sling.startupfilter.disabler [147](R 147.0)] osgi.wiring.package; (&(osgi.wiring.package=org.apache.sling.startupfilter)(version>=1.0.0)(!(version>=2.0.0)))]
at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4112)
at org.apache.felix.framework.Felix.startBundle(Felix.java:2118)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1372)
at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
at java.lang.Thread.run(Thread.java:748)
07.11.2018 11:26:26.863 *INFO * [main] Startup completed

1 Accepted Solution

Avatar

Correct answer by
Level 10

Our Cust Care team looked here. They recommend that you open a ticket so they can investigate this.

View solution in original post

4 Replies

Avatar

Level 10

This looks like an issue in higher environs - you may need a hotfix.

Avatar

Level 10

I am checking with the team to see if this is a known issue.

Avatar

Level 3

Thanks for the reply Scott....what hotfix u meant to suggest over here

Avatar

Correct answer by
Level 10

Our Cust Care team looked here. They recommend that you open a ticket so they can investigate this.