Thanks for the response Steve. It is certainly a good thing to check,
but unfortunately not the issue here.
Actually I know I have the driver correctly configured because I have
been using it successfully for a v. long time :).
My problem is specifically that on *redeploy* of a war file, the
From the look of the stacktrace, which mentions
org.postgresql.Driver.parseURL as the point where the initial exception
was thrown, maybe the URL attribute in your Context's Resource or
ResourceParams might either contain a wrong value or a typo. This might
be leading to a parsing exception, even
