Leo Sutic wrote:
>
>>From: Berin Loritsch [mailto:[EMAIL PROTECTED]]
>>
>>Actually, the fact that it logs at DEBUG is fine. It is there to catch
>>any issues with the Pool code itself. Therefore you don't really want
>>it shoving out several hundreds of messages if you can help it.
>>
>
> The only problem being that any exception thrown in the component's
> initialize()
> method gets logged at DEBUG level.
>
> The behaviour is also dissimilar to ECM's handling of this:
> The ThreadSafeComponentHandler will initialize its singleton instance
> in its own initialize() method. Any exception in the instance's initialize()
> is logged by ECM with an ERROR priority.
>
> The DefaultComponentHandler will allow the Exception thrown from
> initialize() to propagate up where it will be rethrown by ECM, wrapped
> in a ComponentException.
>
> Or - since the PoolableComponentHandler uses the ResourceLimitingPool
> now, is this issue moot as the AbstractPool is deprecated?
>
> (The ResourceLimitingPool will allow an exception thrown by the
> ComponentFactory to propagate upwards and be wrapped in a
> ComponentException,
> so logging works fine there.)
That is probably the most correct thing to do.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
