The error continues to occur, about twice a day or as volume goes up.
The app appears to choke on unfulfilled requests - or open connections
or something: "When connecting to the Database this error was reported:
failed to verify remote server/socket".
The Postgres 7.3.4 database is still working, as the CFMX 6.1 server
continues to use it without issue. All the machines involved are on the
same rack, there's only a router between them. The datasource is set
Per-Request Connections=false, Max Connections=24, Timeouts=20.
It looks like the Tomcat apps get hosed as well... the OpenBD
administrator for THIS deployment stops responding, and OpenBD
administrators for OTHER deployments start throwing directory and file
not found errors... weird stuff.
Would you suggest I try a newer Postgres driver? OpenBD 1.4 is on
postgresql-8.4-701.jdbc4.jar - and the latest is
postgresql-9.0-801.jdbc4.jar. Besides dropping the newer jar into
/WEB-INF/lib - what else needs to be changed?
Was there any general improvements to OpenBD 1.5 in this area? Would you
suggest trying that jar as the next step?
Al
On 8/13/2011 2:30 PM, Alan Holden wrote:
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
