Another thing to add about exception is that we are moving towards runtime exception in 2.0 release (to be in line with the JEE5 approach). Although it is the cache caller that should catch these kind of exceptions but definitely there is higher chance that end users will see some more stack trace. -----Original Message----- From: jbosscache-dev-bounces(a)lists.jboss.org [mailto:jbosscache-dev-bounces@lists.jboss.org] On Behalf Of Manik Surtani Sent: Friday, December 22, 2006 9:38 AM To: Brian Stansberry Cc: jbosscache-dev(a)lists.jboss.org Subject: Re: [jbosscache-dev] Logging exceptions Precisely. If an exception is bubbled up to the point that the stack trace is dumped, then this is not proper design but a real, unexpected exception. As Brian suggested, exceptions that are 'expected' (and while this smells of bad design initially, could still be valid if these are truly infrequent circumstances but need appropriate reaction) would probably be also caught by design, and dealt with. If you are referring to purposefully dumping a stack trace as a part of handling this exception, then keep this to DEBUG or below, as this *does* freak users out! :-) Cheers, -- Manik Surtani Lead, JBoss Cache JBoss, a division of Red Hat Email: manik(a)jboss.org Telephone: +44 7786 702 706 MSN: manik(a)surtani.org Yahoo/AIM/Skype: maniksurtani On 21 Dec 2006, at 19:08, Brian Stansberry wrote: _______________________________________________ jbosscache-dev mailing list jbosscache-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosscache-dev