Thank you for the suggestion, that works indeed, now I can redeploy the
app and the tests work. Of course the security issue for which the guard
object was created is left open (as far as I understood, now other apps
can change my RepositorySelector by using null as the guard), but hey,
life is
Jake, thank you for your enlightenment, but what do you mean by "the
setting of the LoggerFactory"? The LogManager.setRepositorySelector()
method is called only once in my code (which I've largely borrowed from
the examples Mark pointed me to btw).
My LoggerFactory and RepositorySelector subcla
Exactly. Once can also set a 'null' guard in the first place.
At 10:11 AM 9/16/2003 -0500, Jacob Kjome wrote:
At 04:06 PM 9/16/2003 +0300, you wrote:
Now, what in the world does "Cause: java.lang.IllegalArgumentException:
Attempted to reset the LoggerFactory without possessing the guard." mean?
T
At 04:06 PM 9/16/2003 +0300, you wrote:
Now, what in the world does "Cause: java.lang.IllegalArgumentException:
Attempted to reset the LoggerFactory without possessing the guard." mean?
The "guard" is a simple object that protects against re-setting of the
LoggerFactory by anyone but the one who
ass and RepositorySelector impl, in there if you choose to use the workaround above.
Good luck,
Mark
-Original Message-
From: Stefan Puiu [mailto:[EMAIL PROTECTED]
Sent: Monday, September 15, 2003 11:21 AM
To: Log4J Users List
Subject: Re: log4j, JBoss, EJBs
Hello and thank you for the qui
Mark
-Original Message-
From: Stefan Puiu [mailto:[EMAIL PROTECTED]
Sent: Monday, September 15, 2003 12:16 PM
To: Log4J Users List
Subject: Re: log4j, JBoss, EJBs
All static loggers are created in the code, not in the configuration
file, as far as I know, I've included a log4j.xml sam
&m=106340752929541&w=2.
Good luck,
Mark
-Original Message-
From: Stefan Puiu [mailto:[EMAIL PROTECTED]
Sent: Monday, September 15, 2003 12:16 PM
To: Log4J Users List
Subject: Re: log4j, JBoss, EJBs
All static loggers are created in the code, not in the configuration
file, as
Mark
-Original Message-
From: Stefan Puiu [mailto:[EMAIL PROTECTED]
Sent: Monday, September 15, 2003 11:21 AM
To: Log4J Users List
Subject: Re: log4j, JBoss, EJBs
Hello and thank you for the quick reply,
Sorry, I've forgotten to attach my stack trace, here it is now. The
error message
2003 11:21 AM
To: Log4J Users List
Subject: Re: log4j, JBoss, EJBs
Hello and thank you for the quick reply,
Sorry, I've forgotten to attach my stack trace, here it is now. The
error message is quite confusing and probably doesn't indicate the
source of the problem (the class which all
Hello and thank you for the quick reply,
Sorry, I've forgotten to attach my stack trace, here it is now. The
error message is quite confusing and probably doesn't indicate the
source of the problem (the class which allegedly isn't found exists in
the ear file of the application). Yes, JBoss us
Stefan,
I cannot seem to find your stack trace so I am not sure exactly what the nature of
your problem is. I suspect that you have your version of the Logger class in the
system classpath of the JBoss app server. That would require you to restart JBoss.
If your log classes are deployed with
11 matches
Mail list logo
