-
Type:
Suggestion
-
Resolution: Won't Fix
-
None
-
Component/s: None
-
Environment:JBoss 4.0.0
JIRA will not work on JBoss 4.0.0. It dies on startup with this error:
2005-10-18 15:32:54,466 DEBUG [tomcat.localhost./jira.Context] Starting filter 'UrlRewriteFilter'
2005-10-18 15:32:54,716 ERROR [org.apache.commons.digester.Digester] Begin event threw exception
java.lang.ClassNotFoundException: No ClassLoaders found for: org.tuckey.web.filters.urlrewrite.Rule
at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:198)
at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:463)
at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:374)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at org.apache.commons.digester.ObjectCreateRule.begin(ObjectCreateRule.java:252)
at org.apache.commons.digester.Rule.begin(Rule.java:200)
at org.apache.commons.digester.Digester.startElement(Digester.java:1273)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown Source)
Evidently the JBoss copy of Commons Digester is being used in preference to JIRA's (in violation of the servlet spec) and so Digester cannot see the org.tuckey.* classes in JIRA.
This is fixed in JBoss 4.0.1 and above, where JBoss switched to a saner classloading model.
- relates to
-
- Closed
