the relationship between metadata size and heap size
Cantor, Scott
cantor.2 at osu.edu
Mon Sep 14 12:19:12 EDT 2015
On 9/14/15, 12:14 PM, "users on behalf of Ian Young" <users-bounces at shibboleth.net on behalf of ian at iay.org.uk> wrote:
>> On 13 Sep 2015, at 18:39, Cantor, Scott <cantor.2 at osu.edu> wrote:
>>
>> I don't know why it's not logging a simple error if its out of memory
>
>I don't want to focus on this too much, because who knows if it's really what is going on, but one possibility is that the exception is just being caught and discarded. This could be our code, or dependency code, or platform code, just doing a catch (Exception) or catch (Throwable) for some reason and swallowing the result.
>
>I was quite surprised to find that ScheduledThreadPoolExecutor is *defined* to do this by default, for example.
It's that "catch silently" thing I'm having a hard time with. If that's what their code does, they need a good slap.
I'm not saying "container catches it" is a good thing, just saying *we* better not *ever* silently swallow errors and if we are, we need a slap too.
-- Scott
More information about the users
mailing list