[#JRA-8279] JIRA 3.3 and above does not work on JBoss 4.0.0 due to classloader problems with urlrewrite filter

JIRA

JIRA 3.3 and above does not work on JBoss 4.0.0 due to classloader problems with urlrewrite filter

Created: 19/Oct/05 06:40 PM Updated: 08/Sep/07 08:58 PM

Component/s:

None

Affects Version/s:

3.3, 3.4, 3.3.1, 3.3.2, 3.3.3, 3.4 Beta 1

Fix Version/s:

None

Time Tracking:

Not Specified

Environment:

JBoss 4.0.0

Issue Links:

Reference

This issue relates to:

~~JRA-13500~~ Upgrade urlrewritefilter

Participants:	Jeff Turner [Atlassian], Ken Young and Mark Chaimungkalanont [Atlassian]
Since last comment:	58 weeks ago
Resolution Date:	10/Nov/05 07:04 PM
Labels:

Description

« Hide

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.