Hello Robert,
FailureBackoffTime doesn't specify when database connection is tried
next time. After FailureBackoffTime there must be outside trigger to
attempt database connection.
For example in your case you should see ClientListSQL to make a database
connection again after 900 seconds. Can
OK...Upgraded from ActivePerl 5.8 to 5.16 as well as making sure all the
relavent packages were updated as well and updated Radiator from 3.14
to 4.11 -- but I'm still not seeing a reconnect attempt if the service loses
connectivity. So apparently I missed something -- can someone spot what
that
Hello Robert,
On 07/22/2013 05:59 PM, Robert Fisher wrote:
Even though I have the FailureBackoffTime defined to 300 or 5 minutes,
it seems to be ignored.
It is supported on windows. FailureBackoffTime applies when none of the
configured DBs can be connected. The next connection attempt is
Hrmm -- Don't have a trace 4 log, but did see where the logs have a
backing off
for 0 seconds, and my ClientListSQL clause has a refresh of 900 -- but
it's still
not triggering a reconnect, though I do notice I'm running a rather old
version
of 3.14 -- so going to try updating Perl and Radiator
