[
https://issues.apache.org/jira/browse/SLING-11783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17692687#comment-17692687
]
Prasad Shembekar commented on SLING-11783:
------------------------------------------
[~cziegeler] thanks for the response. There is no specific version of servlet
specification mentioned in the web.xml. Please find attached the same.
But, the JBOSS EAP 7.4.0 system module for *javax.servlet.api* is using
{*}jboss-servlet-api_4.0_spec-2.0.0.Final-redhat-00001.jar{*}.
Apache Sling is used along with Jackrabbit + Oracle as the repository and this
in production at many clients places. The clients are already having large
amount of documents stored using Jackrabbit + Oracle. As Apache Sling 9 uses
Jackrabbit OAK, it won't be possible for us to migrate to this version
immediately.
The actual reason for trying this upgrade, is database connection leak issue
which we have observed with Jackrabbit + Oracle. To fix this we are trying to
upgrade the Jackrabbit version to the latest release, so that we can get
support from Jackrabbit team.
Thus this is the first step towards upgrading Apache Sling 6 to 7 and along
with it the bundled Jackrabbit.
But, it would be really helpful if we are able to upgrade only the Jackrabbit
bundles, without requiring to update the Apache Sling version.
> Issue while upgrading version 6 to 7
> -------------------------------------
>
> Key: SLING-11783
> URL: https://issues.apache.org/jira/browse/SLING-11783
> Project: Sling
> Issue Type: Bug
> Components: App CMS, Launchpad
> Reporter: Prasad Shembekar
> Priority: Major
> Attachments: list.xml, pom.xml, server.log, web.xml
>
>
> We are currently using Apache Sling 6 as a war. While trying to upgrade the
> version from 6 to 7,, changed the attached *pom.xml* to use
> "{*}defaultBundleList=7{*}" for the
> *org.apache.sling:maven-launchpad-plugin:2.3.4 (upgraded from 2.0.10 to
> 2.3.4).*
> Updated the dependency for *org.apache.sling:org.apache.sling.launchpad.base
> (from 2.3.0 to 2.5.0).*
> In addition to the default bundles, we are explicitly packaging additional
> bundles using the attached *list.xml.*
> The war builds successfully after making the above changes.
> But when, the war with the *apache sling 7* is deployed to {*}JBOSS EAP
> 7.4.0{*}, the war fails to deploy and exceptions related to bundle
> dependencies are seen. Please see the attached *server.log* file for the
> errors.
> {code:java}
> 2023-02-20 10:26:05,271 ERROR [io.undertow.servlet] (FelixStartLevel) ERROR:
> Error starting
> slinginstall:E:\cover-all\cms\sling\startup\0\org.apache.sling.engine-2.3.6.jar
> (org.osgi.framework.BundleException: Unresolved constraint in bundle
> org.apache.sling.engine [39]: Unable to resolve 39.0: missing requirement
> [39.0] osgi.wiring.package;
> (&(osgi.wiring.package=javax.servlet)(version>=2.3.0)(!(version>=4.0.0)))):
> org.osgi.framework.BundleException: Unresolved constraint in bundle
> org.apache.sling.engine [39]: Unable to resolve 39.0: missing requirement
> [39.0] osgi.wiring.package;
> (&(osgi.wiring.package=javax.servlet)(version>=2.3.0)(!(version>=4.0.0)))
> at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4002)
> at org.apache.felix.framework.Felix.startBundle(Felix.java:2045)
> at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1299)
> at
> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:304)
> at java.lang.Thread.run(Thread.java:748) {code}
> The war for *apache sling 6* is successfully deployed on the same *JBOSS EAP
> 7.4.0* server.
>
> We tried explicitly adding the *javax.servlet* bundle to the *list.xml* at
> {*}level=0{*}, but it also didn't work. Not sure what is missing.
> *Note:* We are upgrading the sling version, in order to update the Jackrabbit
> version. We are seeing some Jackrabbit & database connection leak related
> issues, and thus trying to upgrade the jackrabbit version to the latest. Let
> us know, if Jackrabbit can be directly upgraded instead. It will be really
> helpful
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
