I am really puzzled then. What else can cause a NoClassDefFoundError
exception, for a class that is present inside the commons-collections.jar in
WEB-INF/lib, and only happen in 4.0.2RC1 but not in all other versions?
View the original post :
I have added a new coA.ear (and supporting files) to the JBAS-1551 bug report
that demonstrates both problems:
(1) Logging is still not properly isolated (even in 4.0.2RC1). In 4.0.x there
are no longer any exceptions, and the app controls the logging, but the app log
also incorrectly
My apologies. I seem to be having trouble conveying the problem. This might
be detailed and long, but let me try again:
A) The WAR approach you mention works fine to separate just the logging from
jBoss. I have tested in 3.2.3, 3.2.6, 4.0.0 (finally succeeded in download)
and 4.0.1.
B) The
This is a specific problem with leakage of the commons-logging from tomcat to
the deployment wars. Removal of the commons-logging.jar from the wars results
in a valid scoped deployment as does the use the ears as is with 4.0.1RC2 when
UseJBossWebLoader=false on the
Thanks, this is so close... but not quite.
I used 4.0.1sp1 (newer than 4.0.1rc2, and if I understand correctly it is a
production release rather than beta or release candidate).
1) The release notes in the docs section have a minor error (I noticed it by
comparing the config files of 4.0.0
Just tried 4.0.2RC1... same exact behavior as 4.0.1sp1
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3870404#3870404
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3870404
I tested 4.0.2RC1, not 4.0.1RC1. 4.0.1sp1 does not have the updated tomcat
5.5.x codease which dropped the commons-logging.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3870413#3870413
Reply to the post :
If I understand correctly, you are saying that the problem is not supposed to
exist in 4.0.2RC1. That was not completely my experience.
If you read my last 2 posts you should see that even 4.0.2RC1 still has logging
crossover behavior left - now the application logs are being controlled by
Didn't finish that sentence... being polluted by server-originated messages
... that should be going to the server logs.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3870424#3870424
Reply to the post :
Upon further testing, 4.0.2RC1 is far worse that its predecessors about leaking
its jars to the applications encapsulated in EARs.
The latest leak problem I discovered is now with commons-collections.
Logging-related leaks were bad, but commons-collections is used so widely that
it has
Yes, 4.0.2RC1 worked for me. There is no use of any commons-collection classes
in tomcat 5.5.x:
[EMAIL PROTECTED] jbossweb-tomcat55.sar]$ for j in *.jar; do echo $j; jar -tf
$j | grep SequencedHashMap; done
catalina-manager.jar
catalina-optional.jar
catalina.jar
commons-el.jar
I made some progress, but not as much as I'd like. Here is what I found:
1) The WAR approach in the WIKI above separates the logging, but does not seem
to produce truly separate classloaders... if I have a log4j.jar in my WAR and
is of a different version, or if I have 2 WARs with a class of
I'm using jBoss 4.0.1sp1. My log4j.jar is version 1.2.9.
I played around with the logging. I like to use log4j.properties. I have been
able to seperate the logging between jboss and myapp.war (I'm fairly new to all
this, so have no idea how an EAR works). I have updated the wiki:
The log4j.jar in server/default/lib is 1.2.8.
The log4j.jar in server/default/deploy/myapp.war/WEB-INF/lib is 1.2.9.
The log4j.properties system described in the wiki works even with different
versions of jars being used by jBoss and my application. Does this mean
something?
View the original
I tested it out. If I want to use log4j.properties in my application, I will
HAVE to make the required change in jboss-service.xml, i.e. rename the resource
file that jBoss uses to pick up its log4j settings (conf/log4j.xml -
conf/jboss-log4j.xml).
View the original post :
This is the precedence used by log4j so there is no way to preferentially load
a log4j.properties file using the default search mechanism if there is a
log4j.xml on the classpath search path. We should probably just rename our file
to avoid the conflict.
View the original post :
That should solve this issue.
Thanks.
Regards,
Karan
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3870245#3870245
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3870245
What difference, does it make, if I have different versions of log4j (as
describe in the post above)i.e., a diff version in server/default/lib (call it
version A)and a diff version in server/default/deploy/myapp.war/WEB-INF/lib
(call this version B)?
Since jBoss has already loaded log4j before
karanmg, I used the approach you mention in some of my tests. It seemed to
work for isolating log4j, but did nothing for keeping EARs separate from each
other.
Redefining the problem one more time:
I need total isolation of the contents of the EAR (like J2EE 1.4), including
the logging.
The existing log4j.war example from the wiki works fine for me under
jboss-4.0.1. I have updated the snoop.jsp to display the log4j Logger
codesource and the log4j.xml. Both are seen to come from the war:
h1Log4j Information/h1
Logger CodeSource:
Did you get a solution to your problem?
I am trying to do the same thing with no luck, yet.
I don't want to have to change jBoss's log4j.xml file on every machine I
install my application to. Also, it is much cleaner to maintain everythign
related to your application in the application's dir
Try this:
http://www.jboss.org/wiki/Wiki.jsp?page=Logging
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3868676#3868676
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3868676
I presume what you are saying here is you need a dedicated logging for
yr application without interfrence of JBoss logging.
If thats the case then you need a dedicated appender say
RollingFile Appender.
appender name=YR_FILE class=org.jboss.logging.appender.RollingFileAppender
| ---Path of
No, I am not just talking about separate logging via an appender.
I am talking about being able to have ALL logging jar and configuration in the
WAR/EAR - with ZERO interaction or dependency on jBoss.
As a matter of fact, I am even talking about my application having its own jars
for all
24 matches
Mail list logo
