Thanks for the swift response, guys.
As I recall, the app behaves like it's overwhelmed, other apps in tomcat
are still alive. I'll take another look when it happens again. I'll also
check to see if other database customer apps are hurting at the same
time, and check into Postgres logging.
I suspect a network issue as well, but by "remote", I mean that the
Postgres (Red Hat) server is one bay below the Ubuntu/OpenBD server on
the same rack. The datasource is referencing the server by IP.
When I Google the error verbatim, I get OpenBD threads - so I started
here. But that may just be because this is an OpenBD-specific message.
If so, does (or should) any deeper info get bubbled up somewhere else
AFAYK?
Thanks again,
Al
On 8/13/2011 2:00 PM, Alan Williamson wrote:
Can I advise that when you do see these errors that you jump on that server and
try to telnet to the postgres box
I can tell you that from an engine level, when it loses a connection to the db
it first tries to talk to the remote socket before opening up a true db
connection. If this message is coming up then its network related; its not
getting as far as making a db connection
--
http://alan.blog-city.com/
--
official tag/function reference: http://openbd.org/manual/
mailing list - http://groups.google.com/group/openbd?hl=en
