Clean, OOB Archetype on restart: AuthenticationSupport service missing | Community
Skip to main content
Level 2
December 7, 2021

Clean, OOB Archetype on restart: AuthenticationSupport service missing

  • December 7, 2021
  • 1 reply
  • 1441 views

Mvn; 3.8.4, clear .m2/repository

AEM: 6.5.0

Build cmd used: mvn -B archetype:generate -D archetypeGroupId=com.adobe.aem -D archetypeArtifactId=aem-project-archetype -D archetypeVersion=32 -D appTitle="test" -D appId="test" -D groupId="com.test" -D includeExamples=n -D frontendModule=angular -D aemVersion=6.5.0

It will install, build and run fine but restarting the instance result in failure.

 

The test.core bundle reports this: 


org.apache.sling.api.servlets,version=[2.3,3) -- Cannot be resolved

This is the first error above the AuthenticationSupport message in the error log:

06.12.2021 20:58:00.266 *ERROR* [FelixDispatchQueue] test.core FrameworkEvent ERROR (org.osgi.framework.BundleException: Unable to resolve test.core [583](R 583.0): missing requirement [test.core [583](R 583.0)] osgi.wiring.package; (&(osgi.wiring.package=org.apache.sling.api.servlets)(version>=2.3.0)(!(version>=3.0.0))) Unresolved requirements: [[test.core [583](R 583.0)] osgi.wiring.package; (&(osgi.wiring.package=org.apache.sling.api.servlets)(version>=2.3.0)(!(version>=3.0.0)))])
org.osgi.framework.BundleException: Unable to resolve test.core [583](R 583.0): missing requirement [test.core [583](R 583.0)] osgi.wiring.package; (&(osgi.wiring.package=org.apache.sling.api.servlets)(version>=2.3.0)(!(version>=3.0.0))) Unresolved requirements: [[test.core [583](R 583.0)] osgi.wiring.package; (&(osgi.wiring.package=org.apache.sling.api.servlets)(version>=2.3.0)(!(version>=3.0.0)))]

As mentioned this is pure OOB, no changes have been made to the generated code.  If I backup in a content package and nuke crx-quickstart every time I want to reboot the instance everything will work fine, but I wasn't expecting to have to do that 🙂

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

1 reply

arunpatidar
Community Advisor
Community Advisor
December 7, 2021

Hi,

Could you please check your pom file for dependancy based on your AEM version.

As I know the above version of bundle in 6.5.7 is 

 

<dependency>
	<artifactId>org.apache.sling.api</artifactId>
	<version>2.22.0</version>
	<groupId>org.apache.sling</groupId>
	<scope>provided</scope>
</dependency>
Arun Patidar
BobNoelleAuthor
Level 2
December 16, 2021

Unfortunately I can't include the OOTB pom generated by Adobe because this form mistakenly thinks it's >30k chars.  After deploy, the site (except for /system/xxx) will return 503.  I ended up using v4.0.0 - it doesn't come with so much as a HelloWorld model, but it was easier than trying to untangle the dependency problems with Arch 32.