DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=35774>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=35774





------- Additional Comments From [EMAIL PROTECTED]  2005-08-03 07:24 -------
I haven't had a chance to fully digest this thread, so please forgive me if I'm
way off base.

In the specific scenario Michael described, JCL is available in a classloader
that is a common parent of both apps involved in the "Inter-App" call.  If the
webapp deployed commons-logging-adapters.jar instead of the full
commons-logging.jar there should be no Log incompatibility problems nor any
memory leak.  The logging would end up going to the loggers associated with the
TCCL, which may or may not be the desired behavior.  But that seems more like a
problem with ensuring the TCCL is properly set when a thread crosses an app
boundary and not something JCL can fix. (e.g. it seems to me that if a thread
spawned by a timer service calls into an MBean, the TCCL should be set to the
MBean's classloader before the call is made).

What I'm suggesting of course wouldn't work if JCL wasn't available in a shared
classloader, so I don't mean to imply some of the ideas raised on this thread
are unneeded.  But a commons-logging-adapters.jar approach might be a good
workaround for the issue Michael specifically raised.  (Such a jar doesn't exist
in JCL 1.0.4, the latest official release, but it's simple enough to create one
by taking commons-logging.jar and removing all classes found in
commons-logging-api.jar).

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to