Details
-
Bug
-
Resolution: Done
-
Major
-
JBossAS-3.2.6 Final
-
None
-
None
Description
SourceForge Submitter: pedrosalazar .
Greetings,
I want to introduce a possible bug.
--------------
Introduction:
--------------
I'm trying to isolate a web app as described in
http://www.jboss.org/wiki/Wiki.jsp?page=ClassLoadingConfiguration
The classloader's SourceCode is a good way to verify
it. Another good test is verifing it using log4j inside
the web application file (WEB-INF/lib/log4j.jar and
WEB-INF/classes/log4j.xml). Depending of the
classloader, the global configuration or the local
configuration is used, and we can see how it's working.
----------------------
System information
-----------------------
- Linux RedHat 9.0 (kernel 2.4.26)
- IBM JVM 1.4.2 / SUN JVM 1.4.2
- JBOSS
[ServerInfo] Java version: 1.4.2,IBM Corporation
[ServerInfo] Java VM: Classic VM 1.4.2,IBM Corporation
[ServerInfo] OS-System: Linux 2.4.26,x86
JBoss (MX MicroKernel) [3.2.5 (build:
CVSTag=JBoss_3_2_5 date=200406251954)] Started in 51s:642ms
----------
STEPS
---------
1-In attach I deploy a sample that runs a servlet where
uses log4j and prints messages. It includes the sources.
However, is enough deploy the v1.war..
file: classloading2_jboss.tar.bz2
2-a It works fine if I set the configuration in the
jboss's tomcat configuration:
$jboss_home/server/all/deploy/jbossweb-tomcat50.sar/META-INF/jboss-service.xml
<attribute
name="Java2ClassLoadingCompliance">false</attribute>
<attribute name="UseJBossWebLoader">false</attribute>
The messages should be displayed in jboss server.log if
it doesn't load the log4j.xml inside the webapplication.
A test_v1.log is created and contains the messages.
2-b Using the jboss descriptors (leaving the original
settings in tomcat to "true") to force it to false, it
doesn't work.
The messages are displayed in jboss server.log like it
didn't loaded the log4j.xml inside the webapplication.
[TEST FAILED]
- - both test logs are included in a file resuts.txt
-----------------
Configuration (see sources)
------------------
in jboss-app.xml if deployed as EAR (inside META-INF)
<jboss-app>
<loader-repository>teste:loader=v1.war
<loader-repository-config>
java2ParentDelegation=false
</loader-repository-config>
</loader-repository>
</jboss-app>
in jboss-web if deplyed as WAR:
<jboss-web>
<class-loading java2ClassLoadingCompliance="false">
<loader-repository>
teste:loader=v1.war
<loader-repository-config>java2ParentDelegation=false</loader-repository-config>
</loader-repository>
</class-loading>
</jboss-web>
Regards,
Pedro Salazar