commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Simon Kitching <>
Subject Re: logging, TCCL JCL 1.0.5 alpha
Date Thu, 22 Dec 2005 11:14:46 GMT
Hi Dimitry,

On Wed, 2005-12-21 at 16:32 -0800, Voytenko, Dmytro wrote:
> Hi,
> I'm sorry for repeating the subject if it was discussed already, but I couldn't find
an archive search. 
> This email is regarding numerous problems with JCL in multi-class-loader environments.
This seems to be a rather critical issue. I just got a chance to take a look into changes
for JCL 1.0.5 currently in the alpha stage. Unfortunetely, these changes resolve a very small
percent of all the problems associated with TCCL. If I understand correctly changes mostly
targeted to make sure ClassLoaders are released, thus eliminating memory leaks related to
hot deployment. Other issues (arguably more critical) remain unresolved. 
> Such a behaviour is rather confusing and basically jeopardizes any advantages of configuring
LogFactory-s for each TCCL. This also brings system into the uncertain state. If app1 is redeployed,
it's not clear what will happen to the SharedUtils.log, especially if LogFactory itself will
be weak-referenced (as in 1.0.5). 
> These all problems could be resolved by simply disabling use of TCCL in the LogFactory.
I entered this request in the bug database while ago:
> This problem seems to be rather critical to me, so I was wondering if you have other
plans to resolve these problems, or if you believe the solution described in the bug report
is appropriate. If you're persuing other ways to resolve the issue, could you please point
me to the documents or bug reports describing them? In either case, do you have information
on when the fix could be released?
> thanks,
> Dimitry E Voytenko

There have been a lot of changes since that 1.0.5 alpha branch. It's
better to look at the SVN trunk to see what's happening with JCL.

The next release is likely to be called 1.1, and contain what's
currently in SVN trunk, or very near to it.

With the JCL changes currently in SVN, it is believed that JCL will
correctly handle most cases without the need to disable TCCL loading.
However I agree that there should be some way to completely disable TCCL
loading if necessary, as you describe in your bugzilla entry. I plan to
implement that sometime in early January (assuming that's acceptable to
other JCL developers).

There is definitely interest in getting the JCL 1.1 release out in the
very near future; see the wiki release plan page for example.
Unfortunately no-one has been able to find the time to put the final
touches together but again I hope that I can get that done in January.

If you can help in reviewing code and testing that would be greatly



To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message