Details
- 
    Bug 
- 
    Resolution: Fixed
- 
    Blocker 
- 
    13.1-rc-1
- 
    java11; reproduces with Debian package for 13.10.3 with MariaDB 10.3 as DB and jetty-hsql for 14.1, both with Ubuntu 20.04 OS; openjdk 11.0.14 2022-01-18
- 
        Unknown
- 
        N/A
- 
        N/A
- 
        
Description
Reporting it as platform issue despite the error comes from an extension: https://extensions.xwiki.org/xwiki/bin/view/Extension/VFS%20API
as the "issues" link on that extension page points to the XWIKI project.
When having the VFS API extension installed, XWiki fails to initialize with the error message:
2022-03-09 12:12:22.348:WARN :oejw.WebAppContext:main: Failed startup of context o.e.j.w.WebAppContext@31fa1761{XWiki,/xwiki,file:///opt/apps/xwiki/14.1-xwiki-platform-distribution-jetty-hsqldb/webapps/xwiki/,UNAVAILABLE}{/opt/apps/xwiki/14.1-xwiki-platform-distribution-jetty-hsqldb/./webapps/xwiki}
java.util.ServiceConfigurationError: No service located for interface net.java.truevfs.kernel.spec.spi.FsManagerFactory.
	at global.namespace.service.wight.core.ServiceLocator.providers(ServiceLocator.java:128)
	at global.namespace.service.wight.core.ServiceLocator.provider(ServiceLocator.java:115)
	at global.namespace.service.wight.core.ServiceLocator.provider(ServiceLocator.java:110)
	at net.java.truevfs.kernel.spec.sl.FsManagerLocator$Lazy.<clinit>(FsManagerLocator.java:40)
	at net.java.truevfs.kernel.spec.sl.FsManagerLocator.get(FsManagerLocator.java:35)
	at net.java.truevfs.access.TConfig.<init>(TConfig.java:246)
	at net.java.truevfs.access.TConfig.<clinit>(TConfig.java:208)
	at org.xwiki.vfs.internal.VfsAttachDriverRegistrationListener.initialize(VfsAttachDriverRegistrationListener.java:88)
	at org.xwiki.component.embed.InitializableLifecycleHandler.handle(InitializableLifecycleHandler.java:39)
	at org.xwiki.component.embed.EmbeddableComponentManager.createInstance(EmbeddableComponentManager.java:365)
	at org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:451)
	at org.xwiki.component.embed.EmbeddableComponentManager.getInstanceMap(EmbeddableComponentManager.java:242)
	at org.xwiki.component.embed.EmbeddableComponentManager.getInstanceList(EmbeddableComponentManager.java:225)
	at org.xwiki.observation.internal.DefaultObservationManager.initializeListeners(DefaultObservationManager.java:166)
	at org.xwiki.observation.internal.DefaultObservationManager.getListenersByEvent(DefaultObservationManager.java:132)
	at org.xwiki.observation.internal.DefaultObservationManager.notify(DefaultObservationManager.java:283)
	at org.xwiki.component.internal.StackingComponentEventManager.sendEvent(StackingComponentEventManager.java:151)
	at org.xwiki.component.internal.StackingComponentEventManager.flushEvents(StackingComponentEventManager.java:92)
	at org.xwiki.container.servlet.XWikiServletContextListener.contextInitialized(XWikiServletContextListener.java:124)
	at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:1043)
(Stack trace is for jetty/hsql; error for debian package looks similar.)
Afterwards one only gets a 404 when trying to access the XWiki webapp.
The only workaround to get XWiki back running was to edit the file
${PERMDIR}/extension/repository/org%2Exwiki%2Eplatform%3Axwiki-platform-vfs-api/14%2E1/org%2Exwiki%2Eplatform%3Axwiki-platform-vfs-api-14%2E1.xed
in the permanent directory (path might be different depending on version) and change the line:
<installed.installed type="boolean">true</installed.installed>
to
<installed.installed type="boolean">false</installed.installed>
Afterwards the API is of course no longer available, but at least XWiki starts again.
If installing the extension on a running XWiki the problem seem not to appear, but the next restart will fail.
Attachments
Issue Links
- is caused by
- 
                    XWIKI-18284 Upgrade to TrueVFS 0.14.0 -         
- Closed
 
-