[jbosscache-dev] JBCACHE-710

[Ben Wang]

Bummer! This is 3 months old and I'd say my memory has faded a bit. :-( And it is not easy to reproduce as well unless there is a way to screw up the FCL .dat file. I remember loader.remove() somehow doesn't throw an exception there and therefore the code moves on to notifyActivate and trigger the recursive loop.

Since now that we have documented the FCL limitation, maybe we can downgrade the serverity and push it back to later releases. This is a bug associated mostly with FLC. If I run into that problem again, I will raise it up.

Thanks,

-Ben

-----Original Message-----
From: jbosscache-dev-bounces at lists.jboss.org [mailto:jbosscache-dev-bounces at lists.jboss.org] On Behalf Of Manik Surtani
Sent: Friday, October 27, 2006 6:56 PM
To: jbosscache-dev at lists.jboss.org
Subject: [jbosscache-dev] JBCACHE-710

Ben,

Trying to understand the problem here, assuming an AS restart leaves the FCL .dat file in an inconsistent state, wouldn't the loader.remove
() throw an exception anyway?  And this would propagate up, since the
remove() method in the ActivationInterceptor does throw an Exception ...


--
Manik Surtani

Lead, JBoss Cache
JBoss, a division of Red Hat

Email: manik at jboss.org
Telephone: +44 7786 702 706
MSN: manik at surtani.org
Yahoo/AIM/Skype: maniksurtani


_______________________________________________
jbosscache-dev mailing list
jbosscache-dev at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosscache-dev