java.lang.ClassCastException: org.jboss.logging.appender.Dai JBossJavaXMLWeb
程序员文章站
2022-07-15 14:23:27
...
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.
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.lang.ClassCastException: org.jboss.logging.appender.Dai JBossJavaXMLWeb
-
dubbo java.lang.ClassCastException: java.lang.String cannot be cast to java.lan
-
dubbo java.lang.ClassCastException: java.lang.String cannot be cast to java.lan
-
java.lang.ClassCastException:org.apache.catalina.util.DefaultAnnotationProcessor
-
java.lang.ClassCastException: java.util.ArrayList cannot be cast to com.github.pagehelper.Page
-
整合SSH java.lang.ClassCastException: xxx_$$_javassist_0 cannot be cast to javassist.util.proxy.Proxy
-
spring boot从redis取缓存发生java.lang.ClassCastException异常
-
java.lang.ClassCastException: weblogic.net.http.SOAPHttpsURLConnection cannot be
-
android ListView分页出现java.lang.ClassCastException
-
weblogic启动用户不对导致的weblogic报java.lang.ClassCastException