Problem with cq start up on installation of SP3 on AEM 6.3 | Community
Skip to main content
sai111
Level 2
November 7, 2018
Solved

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

  • November 7, 2018
  • 4 replies
  • 2264 views

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

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 smacdonald2008

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

4 replies

smacdonald2008
Level 10
November 7, 2018

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

smacdonald2008
Level 10
November 7, 2018

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

sai111
sai111Author
Level 2
November 8, 2018

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

smacdonald2008
smacdonald2008Accepted solution
Level 10
November 8, 2018

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