Thank you so much Alin.
On Fri, Nov 28, 2008 at 1:15 AM, Alin Dreghiciu <[EMAIL PROTECTED]>wrote:
> Changed. Please test. I will close the issue and you should reopen it
> if it does not work.
>
> On Thu, Nov 27, 2008 at 8:04 PM, Alin Dreghiciu <[EMAIL PROTECTED]>
> wrote:
> > ConcurrentHashMap i
Changed. Please test. I will close the issue and you should reopen it
if it does not work.
On Thu, Nov 27, 2008 at 8:04 PM, Alin Dreghiciu <[EMAIL PROTECTED]> wrote:
> ConcurrentHashMap is only in Java 5 and Pax Logging is Java 1.4.
> More, I guess, The WeakHashMap is used so the Log isntances cre
ConcurrentHashMap is only in Java 5 and Pax Logging is Java 1.4.
More, I guess, The WeakHashMap is used so the Log isntances created by
LogFactory to be garbage collected when not in use anymore, so the
concurrent hash map will eliminate this behavior.
Maybe let's just try first to use a synchroniz
2008/11/28 Hendy Irawan <[EMAIL PROTECTED]>
> IIRC I ever faced a similar problem sometime ago.
>
> The way I make this happen is by loading a bunch of JARs using
> ModuleFusion's DirInstaller.
>
> This problem is intermittent, happens about 50% of the time.
>
> Should I post a bug report?
>
yep
