On Fri, Dec 21, 2012 at 2:35 PM, Laird Nelson <ljnelson_at_gmail.com> wrote:
> On Fri, Dec 21, 2012 at 2:30 PM, Marina Vatkina <marina.vatkina_at_oracle.com
> > wrote:
>
>> It might be just an internal wrapper.
>>
>
> I don't see any further root cause exceptions, however (the snippet I
> quoted is the root-most exception). I'd expect if this were just a wrapper
> the underlying exception SOMEWHERE would still show itself?
>
Chalking this one up to gremlins; cannot reproduce manually. I'm
suspecting that a connection got interrupted somewhere and that this is the
root cause.
Since flushing the connection pool is a known bug (i.e. there's no way from
the admin console to flush a pool without causing an error; see
http://java.net/jira/browse/GLASSFISH-14130 for an example; this is true
even of our initialized pools on 3.1.2.2), can I somehow tell GlassFish to
dump and refill the pool at the first sign of connection trouble? I didn't
see anything obvious in
http://docs.oracle.com/cd/E26576_01/doc.312/e24928/jdbc.htm#gharo.
Best,
Laird
--
http://about.me/lairdnelson