Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Message-ID: <25908899.1163790106714.JavaMail.jira@brutus>
Date: Fri, 17 Nov 2006 11:01:46 -0800 (PST)
From: "Dennis Lundberg (JIRA)" <jira@apache.org>
To: commons-dev@jakarta.apache.org
Subject: [jira] Closed: (LOGGING-65) [logging] Disabling of TCCL
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/LOGGING-65?page=all ]

Dennis Lundberg closed LOGGING-65.
----------------------------------

    Assignee: Simon Kitching

> [logging] Disabling of TCCL
> ---------------------------
>
>                 Key: LOGGING-65
>                 URL: http://issues.apache.org/jira/browse/LOGGING-65
>             Project: Commons Logging
>          Issue Type: Bug
>    Affects Versions: 1.0.4
>         Environment: Operating System: other
> Platform: Other
>            Reporter: Dimitry E Voytenko
>         Assigned To: Simon Kitching
>             Fix For: 1.1.0
>
>
> I separated this request from 35774 as it seems to provide a viable and easy 
> solution to a big number of ClassLoader-related problems of using JCL in shared 
> environments. The solution relies on having an option (configured via system 
> properties) to disable TCCL usage and only use LogFactory's ClassLoader. When 
> TCCL is disabled, logger implementation and caching should be performed in the 
> JCL's ClassLoader only (cache will be reduced to a single record). This would 
> remove any memory leak issues as well as other inconsitencies (see 35774 for 
> some samples). 
> There're two main scenarios how JCL is used in the shared environment: a) 
> deployed in the shared class loader (shared for Tomcat and UCL for JBoss), b) 
> deployed in the application's class loader in the child-first ClassLoader 
> setup. In both cases this solution works well and disabled TCCL could even be a 
> reasonable default (though it depends on other uses). In case of deployment 
> within application's classloader (case [b]), two versions of JCL can coexist 
> redirecting logs for the application's classes to application's LogFactory 
> instance and shared classes to shared LogFactory.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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