Hi Paul,
Am 12.05.2011 09:56, schrieb Paul Merlin:
> Quoting "Manfred Riem"<mriem_at_manorrock.org>:
>> Hence my admonition to investigate which library is causing it.
>
> I would definetely go that way and either push a fix upstream or eradicate this
> library from my toolset.
In an ideal world: yes.
Unfortunately, we don't have time for in-depth debugging of 3rd-party
libraries. That just opens a Pandora's Box of endless analysis and might
force us to do an in-depth research on every 3rd-party-lib we do or like
to use. Which renders the benefit in effort of simply picking a OSS
library useless.
And even if we go down that path and debug that or these libs that cause
the problem and point the library owners to it: some of them never
intended to have it used in a JEE environment or simply don't want it to
be fixed as it would break their architecture or whatever reasons they
come up with.
And I think I would probably have to argue with some of them, about
whether the problem really is a bug of their library or rather a
Glassfish issue.
To make a long story short: The workaround (restart at 1am) outweighs
the cost of bugfixing 3rd-party libs for us. YMMV.
Best regards,
Matthias