I downloaded and installed http://extensions.xwiki.org/xwiki/bin/view/Extension/Filter%20Application
Now XWiki won’t start when the web application server is restarted:
[2018-01-12T14:00:56.335-0800] [Payara 4.1] [INFO] [] [] [tid: _ThreadID=99 _ThreadName=XWiki initialization] [timeMillis: 1515794456335] [levelValue: 800] [[
2018-01-12 14:00:56,335 [XWiki initialization] ERROR cumentTranslationBundleFactory - Failed to load existing translations
org.xwiki.query.QueryException: Exception while executing query. Query statement = [ select distinct doc.fullName from XWikiDocument as doc , BaseObject as translation WHERE 1=1 and doc.fullName=translation.name and translation.className='XWiki.TranslationDocumentClass' ]
Full stack trace is at: https://pastebin.com/raw/yE1QPU1j
The hibernate.cfg.xml file validates through the W3C XML validator.
Additionally, the following message occurs in the log:
[2018-01-12T14:00:56.350-0800] [Payara 4.1] [SEVERE] [] [] [tid: _ThreadID=99 _ThreadName=XWiki initialization] [timeMillis: 1515794456350] [levelValue: 1000] [[
java.lang.IllegalStateException: zip file closed
The only file that was modified within the last ten days is:
find . -type f -mtime -10
./xwiki/WEB-INF/xwiki.cfg
Any ideas how to resolve this issue or put XWiki back in a “safe mode” without any extensions installed?
Software:
- xwiki-9.10.1
- postgresql-42.1.4
- payara-4.1.2.174
- java version “1.8.0_131”
Caused by: org.hibernate.HibernateException: Could not parse configuration: /WEB-INF/hibernate.cfg.xml
Are you sure the stack trace is complete ? Usually in this case you also get some details on why exactly hibernate could not parse the hibernate file.
Are you sure the stack trace is complete ? Usually in this case you also get some details on why exactly hibernate could not parse the hibernate file.
I think it is probably a red herring. I’ve pasted the complete log: https://paste.ee/r/igYdY (800KB)
There does not appear to be any issue with the config file – it also hasn’t been modified in the last ten days and since it was working on Friday morning and hasn’t been modified, I suspect the error lies elsewhere.
The HTTP error screen shows:
HTTP Status 500 - Internal Server Error
type Exception report
messageInternal Server Error
description The server encountered an internal error that prevented it from fulfilling this request.
exception
java.lang.IllegalStateException: zip file closed
note The full stack traces of the exception and its root causes are available in the Payara Server > 4.1.1.171.1 #badassfish logs.
Other interesting log lines include:
- java.io.IOException: Resource does not exist: bundle://51.0:1/
- Collision between core extension [javax.xml.bind:jaxb-api/2.2.13-b141020.1521 (jar:file:/opt/payara41/glassfish/modules/endorsed/jaxb-api.jar!/META-INF/maven/javax.xml.bind/jaxb-api/pom.xml)] and [javax.xml.bind:jaxb-api/2.3.0 (file:/opt/payara41/glassfish/domains/domain1/applications/xwiki/WEB-INF/lib/jaxb-api-2.3.0.xed)]]]
- Unexpected error when trying to find extension [org.glassfish.metro:webservices-api-osgi/2.3.2-b608] in repository [maven-xwiki:maven:Index of /groups/public
Note that the wiki server is an offline server, so if it needs connectivity to nexus.wiki.org, that needs to be documented somewhere, but shouldn’t cause the application to fail. Perhaps a warning message on a the wiki’s home page would suffice.
Help is greatly appreciated.
if it needs connectivity to nexus.wiki.org
It does not “need” it unles you plan to use Extension Manager to install extensions since many of them have dependencies located on nexus.xwiki.org. If you don’t plan to use Extension Manager then you should disabled default extensions repositories in xwiki.properties to avoid any related log (i.e. XWiki won’t try to access not accessible repositories anymore).
that needs to be documented somewhere
It is documented on http://www.xwiki.org/xwiki/bin/view/Documentation/AdminGuide/Installation/#HRunningXWikibehindproxy-server.