Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

Issue while upgrading from AEM 6.3 TO 6.5

Shallu_Rohilla
Level 4
Level 4

Hi,

We are doing AEM upgrade from version 6.3 to 6.5. Also moving from Jboss to Tomcat.(AEM 6.5 author is on Tomcat). While starting up the server, we are getting this exception:

22.05.2020 02:30:08.686 *ERROR* [FelixDispatchQueue] org.apache.sling.startupfilter.disabler FrameworkEvent ERROR (org.osgi.framework.BundleException:
Unable to resolve org.apache.sling.startupfilter.disabler [146](R 146.0):
missing requirement [org.apache.sling.startupfilter.disabler [146](R 146.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 [52](R 52.1):
missing requirement [org.apache.sling.startupfilter [52](R 52.1)] osgi.wiring.package;
(&(osgi.wiring.package=javax.servlet)(version>=3.1.0)(!(version>=4.0.0)))] Unresolved requirements:
[[org.apache.sling.startupfilter.disabler [146](R 146.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 [146](R 146.0):
missing requirement [org.apache.sling.startupfilter.disabler [146](R 146.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 [52](R 52.1): missing requirement
[org.apache.sling.startupfilter [52](R 52.1)] osgi.wiring.package; (&(osgi.wiring.package=javax.servlet)(version>=3.1.0)
(!(version>=4.0.0)))] Unresolved requirements: [[org.apache.sling.startupfilter.disabler [146](R 146.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:4368)
at org.apache.felix.framework.Felix.startBundle(Felix.java:2281)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1539)
at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
at java.lang.Thread.run(Thread.java:748)

 

Any help would be appreciated.

 

Just to add we tried this : https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-6-2-and-java-1-8/qaq-p...

We couldn't find any such property in sling.properties.

Regards,

Shallu Rohilla

6.5
1 Accepted Solution
gspatil11
Correct answer by
Level 2
Level 2

We have changed tomcat attribute: strictServletCompliance as false and that has resolved the issue with javax.servlet version>=3.1.0. We are using javax.servlet version:3.0 now on same Tomcat instance.

View solution in original post

13 Replies
ArpitVarshney
Community Advisor
Community Advisor

Hi @Shallu_Rohilla 

 

Can you try installing the latest service pack of AEM 6.5? 

I've recently upgraded AEM 6.3 to AEM 6.5.4 and didn't face any such issue.

 

Also please confirm:

  • Are you doing an in-place upgrade or moving the content over packages?
  • is this issue happening after installing the your custom code?

 

Regards,

Arpit Varshney

gspatil11
Level 2
Level 2

Hi Mate, 

 

Please find below responses to your questions.

 

Can you try installing the latest service pack of AEM 6.5? I've recently upgraded AEM 6.3 to AEM 6.5.4 and didn't face any such issue.

- We are not able to access CRX/de, System console or package manager We are getting HTTP Status 503 – Service Unavailable

 

Also please confirm: Are you doing an in-place upgrade or moving the content over packages?

- This is inplace upgrade

is this issue happening after installing the your custom code?

- We already have all the code in this environment. This is running performance testing environment

 

Issue occurrence: After upgrade steps, while instance is starting up we could see this error.

We have followed the steps as per: https://docs.adobe.com/content/help/en/experience-manager-65/deploying/upgrading/app-server-upgrade....

ArpitVarshney
Community Advisor
Community Advisor

Hi @gspatil11 @Shallu_Rohilla 

 

You can try the below step to add a service pack.

  • Stop your instance.
  • Download the latest service pack.
  • Create a folder named “install” inside the “crx-quickstart” folder [this is folder is present in the same location of jar file].
  • Copy the SP zip file downloaded in Step 2 inside the install folder. [Please create an install folder if it is not present]
  • Start AEM

Regards,

Arpit

javi
Level 1
Level 1
HI gspatil11 did you find something here?, we also have the same issue. Thank you.
Jörg_Hoh
Employee
Employee

 

Hi,

 

the problem is:

(&(osgi.wiring.package=javax.servlet)(version>=3.1.0)(!(version>=4.0.0)))]

 

what version of Tomcat do you use? 

 

From what I see in the specification at https://tomcat.apache.org/whichversion.html, only Tomcat 8.0.x and 8.5 are eligible, as any newer version brings javax.servlet 4.0 specification (which is not supported according to this version range). And according to the support matrix at https://helpx.adobe.com/experience-manager/6-3/sites/deploying/using/technical-requirements.html only Tomcat 8.5 is supported.

 

gspatil11
Level 2
Level 2
Hi Jorg, We are using Tomcat 8.5.41 version and AEM 6.3 was running fine on this instance before upgrade
Shallu_Rohilla
Level 4
Level 4

So, our current AEM version is 6.5 and tomcat version is 8.5.41 which should be supported as per AEM documentation.

Jörg_Hoh
Employee
Employee
Can you please paste a screenshot of the details of the Bundle "Apache Sling Startup Filter" from your 6.3 environment?
gspatil11
Correct answer by
Level 2
Level 2

We have changed tomcat attribute: strictServletCompliance as false and that has resolved the issue with javax.servlet version>=3.1.0. We are using javax.servlet version:3.0 now on same Tomcat instance.

View solution in original post

Jörg_Hoh
Employee
Employee
Great, that you got it resolved. Strange behavior anyway, because you are working on a fully supported platform.