Hi Felix,

Thanks for fixing the dependency.

But at last I didn't update the Jackrabbit version to 2.2.2, as the updated
'Jackrabbit Core' and 'Sling JCR Server' were creating conflict with some of
the Sling modules and as a result Sling wasn't running properly. We found
the following error message in the homepage of Sling:
'*HTTP Status 503 - AuthenticationSupport service missing. Cannot
authenticate request*.'

In the Sling log file, I was getting the following stack traces:

19.02.2011 22:21:39.873 *ERROR* [FelixDispatchQueue]
org.apache.felix.webconsole.plugins.memoryusage FrameworkEvent ERROR
(org.osgi.framework.ServiceException: Service factory exception:
javax/servlet/ServletRequest) org.osgi.framework.ServiceException: Service
factory exception: javax/servlet/ServletRequest
at
org.apache.felix.framework.ServiceRegistrationImpl.getFactoryUnchecked(ServiceRegistrationImpl.java:314)
at
org.apache.felix.framework.ServiceRegistrationImpl.getService(ServiceRegistrationImpl.java:221)
at
org.apache.felix.framework.ServiceRegistry.getService(ServiceRegistry.java:297)
at org.apache.felix.framework.Felix.getService(Felix.java:3007)
at
org.apache.felix.framework.BundleContextImpl.getService(BundleContextImpl.java:329)
at
org.osgi.util.tracker.ServiceTracker.addingService(ServiceTracker.java:442)
at
org.apache.felix.http.whiteboard.internal.tracker.AbstractTracker.addingService(AbstractTracker.java:35)
at
org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:896)
at
org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:261)
at
org.osgi.util.tracker.AbstractTracked.trackInitial(AbstractTracked.java:184)
at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:339)
at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:273)
at
org.apache.felix.http.whiteboard.internal.WhiteboardActivator.addTracker(WhiteboardActivator.java:56)
at
org.apache.felix.http.whiteboard.internal.WhiteboardActivator.doStart(WhiteboardActivator.java:48)
at
org.apache.felix.http.base.internal.AbstractActivator.start(AbstractActivator.java:41)
at
org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:629)
at org.apache.felix.framework.Felix.activateBundle(Felix.java:1827)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1744)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1148)
at org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.NoClassDefFoundError: javax/servlet/ServletRequest
at
org.apache.felix.webconsole.plugins.memoryusage.internal.Activator$2.createObject(Activator.java:59)
at
org.apache.felix.webconsole.plugins.memoryusage.internal.Activator$AbstractServiceFactory.getService(Activator.java:120)
at
org.apache.felix.framework.ServiceRegistrationImpl.getFactoryUnchecked(ServiceRegistrationImpl.java:310)
... 20 more
Caused by: java.lang.ClassNotFoundException: javax.servlet.ServletRequest
not found by org.apache.felix.webconsole.plugins.memoryusage [66]
at
org.apache.felix.framework.ModuleImpl.findClassOrResourceByDelegation(ModuleImpl.java:787)
at org.apache.felix.framework.ModuleImpl.access$400(ModuleImpl.java:71)
at
org.apache.felix.framework.ModuleImpl$ModuleClassLoader.loadClass(ModuleImpl.java:1768)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
... 23 more

And

19.02.2011 22:21:39.880 *INFO* [Repository Pinger]
org.apache.sling.jcr.jackrabbit.server pingAndCheck; loginAdministrative
failed (javax.jcr.LoginException: LoginModule ignored Credentials)
javax.jcr.LoginException: LoginModule ignored Credentials
at org.apache.jackrabbit.core.RepositoryImpl.login(RepositoryImpl.java:1489)
at
org.apache.sling.jcr.base.AbstractSlingRepository.login(AbstractSlingRepository.java:214)
at
org.apache.sling.jcr.base.AbstractSlingRepository.loginAdministrative(AbstractSlingRepository.java:180)
at
org.apache.sling.jcr.base.AbstractSlingRepository.pingAndCheck(AbstractSlingRepository.java:517)
at
org.apache.sling.jcr.base.AbstractSlingRepository.startRepository(AbstractSlingRepository.java:804)
at
org.apache.sling.jcr.base.AbstractSlingRepository.run(AbstractSlingRepository.java:925)
at java.lang.Thread.run(Thread.java:619)
Caused by: javax.security.auth.login.FailedLoginException: LoginModule
ignored Credentials
at
org.apache.jackrabbit.core.security.authentication.LocalAuthContext.login(LocalAuthContext.java:87)
at org.apache.jackrabbit.core.RepositoryImpl.login(RepositoryImpl.java:1472)
... 6 more

And

19.02.2011 22:21:43.897 *ERROR* [http-8080-exec-1]
org.apache.sling.engine.impl.SlingHttpContext handleSecurity:
AuthenticationSupport service missing. Cannot authenticate request.

So, what I did is I fixed the Jackrabbit Core's (2.1.1 version)
isExpiredmethod of
org.apache.jackrabbit.core.lock.LockInfo class and build Sling with that. It
somewhat fixed the locking issue that I was facing earlier. But I think
still there are a number of issues left there. So, it'll be best if someone
can update the Jacrabbit dependencies to the latest version in Sling.

Thanks & Regards.

On Fri, Feb 18, 2011 at 9:29 PM, Felix Meschberger <[email protected]>wrote:

> Hi,
>
> Am Freitag, den 11.02.2011, 16:22 +0000 schrieb Gazi Mushfiqur Rahman:
> > So now the latest and bug free jackrabbit-core is being used. But now I
> > found that a framework error is occurring as below:
> >
> >
> >
> > 11.02.2011 21:12:50.569 *ERROR* [FelixDispatchQueue]
> > org.apache.aries.jmx.core FrameworkEvent ERROR
> > (org.osgi.framework.BundleException: Unresolved constraint in bundle
> > org.apache.aries.jmx.core [7]: Unable to resolve 7.0: missing requirement
> > [7.0] package;
> > (&(package=org.apache.aries.util)(version>=0.3.0)(!(version>=1.0.0))))
> > org.osgi.framework.BundleException: Unresolved constraint in bundle
> > org.apache.aries.jmx.core [7]: Unable to resolve 7.0: missing requirement
> > [7.0] package;
> > (&(package=org.apache.aries.util)(version>=0.3.0)(!(version>=1.0.0)))
>
> When I upgraded the dependencies to aries JMX 0.3.0 I failed to
> recognize this requirement (and failed to see this failure in the log
> file ...). In the meantime I fixed this and the util bundle should be
> part of the launchpad builder build.
>
> Regards
> Felix
>
>

Reply via email to