logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ceki Gülcü <c...@qos.ch>
Subject Re: log4j, JBoss, EJBs
Date Tue, 16 Sep 2003 15:16:15 GMT

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?
>
>The "guard" is a simple object that protects against re-setting of the 
>LoggerFactory by anyone but the one who set it first with a particular 
>"guard".  Basically, this would allow a container to set the 
>LoggerFactory, but disallow applications running in the container from 
>changing it.  If the container holds a handle on the "guard" object, then 
>it alone can change the LoggerFactory.  If no one holds a handle on the 
>"guard" object, then no one can change the LoggerFactory once it is set 
>the first time.
>
>The setting of the LoggerFactory is, obviously, being called multiple 
>times.  Either avoid the multiple calls, catch and ignore the exception, 
>or hold a handle to the "guard" object and re-set the LoggerFactory each 
>time (probably not necessary or desired).
>
>Jake

-- 
Ceki Gülcü

      For log4j documentation consider "The complete log4j manual"
      ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp

      import org.apache.Facetime;
      ApacheCon US 2003, 18-21 November http://apachecon.com/



---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-user-help@jakarta.apache.org


Mime
View raw message