Issue while upgrading from AEM 6.3 TO 6.5 | Community
Skip to main content
S
Shallu_Rohilla
Level 4
May 22, 2020
Solved

Issue while upgrading from AEM 6.3 TO 6.5

  • May 22, 2020
  • 3 replies
  • 11535 views

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/277087

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

Regards,

Shallu Rohilla

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 gspatil11-1

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.

3 replies

ArpitVarshney
Community Advisor
ArpitVarshneyCommunity Advisor
Community Advisor
May 22, 2020

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

    G
    gspatil11-1
    Level 2
    May 22, 2020

    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.html

    joerghoh
    Adobe Employee
    joerghohAdobe Employee
    Adobe Employee
    May 22, 2020

     

    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.

     

      S
      Shallu_RohillaAuthor
      Level 4
      May 22, 2020
      But we are following Adobe documentation which says tomcat 8.5.x. As we have deployed version 6.5. https://docs.adobe.com/content/help/en/experience-manager-65/deploying/introduction/technical-requirements.html
      G
      gspatil11-1Accepted solution
      Level 2
      May 28, 2020

      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.

        joerghoh
        Adobe Employee
        joerghohAdobe Employee
        Adobe Employee
        May 28, 2020
        Great, that you got it resolved. Strange behavior anyway, because you are working on a fully supported platform.
        Terms & ConditionsAccessibility statement

        Loading footer...