本文介绍了解决JBoss中类加载器问题的一种方法，通过将配置文件<jboss>/server/default/jbossweb-tomcat55.sar/META-INF/jboss-service.xml中的Java2ClassLoadingCompliance和UseJBossWebLoader属性设置为true，可以恢复到旧的类加载模型。请注意这可能会影响部署在JBoss上的其他应用。
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.
扫一扫
5万+
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
