[ic] mysql having problems reconnecting on catalog reconfig
mike at perusion.com
Thu Nov 10 18:50:25 UTC 2011
Quoting Peter (peter at pajamian.dhs.org):
> On 11/11/11 03:15, Mike Heins wrote:
> > It's a part of the alternate DSN stuff, where you can fall back to a
> > different database server if one is down.
> Well it does seem to make at least some sense to me that if the first db
> server goes down to retry the connection to that before falling back to
> an alternate DSN or giving up entirely.
I believe our approach is that we delegate that level of connection
robustness to the DBI module.
> > But the bigger question is -- why did your connect fail originally,
> > so that you have a connection marked as bad?
> Yes, I agree, unfortunately I'm at a loss for how to discover this. It
> took enough digging for me to find this bit of code.
> That said, I highly suspect it has something to do with either (1) newer
> version of perl, (2) newer version of DBI or (3) newer version of
> DBD::mysql (I don't think it's this last one because I initially
> suspected it and went back about 10 versions and the issue was still there).
Did you see my suggestion about emptying %DBI_connect_bad on a
Perusion -- Expert Interchange Consulting http://www.perusion.com/
phone +1.765.328.4479 <mike at perusion.com>
Life isn't fair, but it's good. -- Regina Brett
More information about the interchange-users