java.lang.ClassCastException: org.jboss.logging.appender.Dai

One way to solve the classloader issue is by reverting the JBoss configuration to the old classloading model.
Edit the file <jboss>/server/default/jbossweb-tomcat55.sar/META-INF/jboss-service.xml
Change the following lines:
<attribute name="Java2ClassLoadingCompliance">true</attribute>
<attribute name="UseJBossWebLoader">true</attribute>
(both are default set to false in jboss-4.0.2).

Note: this is a global setting for JBoss, so if you have more .war's deployed in JBoss, this might affect them too. If that is a problem for you, you could make this change for jira only, by editing the jboss-web.xml in the jira war; see JBoss site for more details.

[ Show & ] Peter Doornbosch [02/Mar/06 04:18 AM] One way to solve the classloader issue is by reverting the JBoss configuration to the old classloading model. Edit the file <jboss>/server/default/jbossweb-tomcat55.sar/META-INF/jboss-service.xml Change the following lines: <attribute name="Java2ClassLoadingCompliance">true</attribute> <attribute name="UseJBossWebLoader">true</attribute> (both are default set to false in jboss-4.0.2). Note: this is a global setting for JBoss, so if you have more .war's deployed in JBoss, this might affect them too. If that is a problem for you, you could make this change for jira only, by editing the jboss-web.xml in the jira war; see JBoss site for more details.

你可能感兴趣的:(java,xml,Web,jboss)