Mamoru Tasaka wrote:
Michael Stahnke wrote, at 05/20/2010 03:54 AM +9:00:
> I've trying to look at this bug.
> I think an option is simply to create a rails2.3 package. I realize
> this probably less than ideal, but the only real solution I see for
> the problem. Thoughts?
Well, I don't oppose to making parallel-installable rails 2.3.x related
packages on EPEL itself.
However I don't know if EPEL's policy allows such decision like "We made
rails 2.3.x packages so please use them. Althogh rails 2.1.x is still
on EPEL5, well, WONTFIX" (note that I don't know EPEL's
I guess even if rails 2.3.x packages are imported into EPEL5, if bug 572722
is due to bug in rails 2.1.x it should be fixed anyway and so the cause
of bug 572722 should be investigated anyway.
I've tried to determine what the actual cause is here, and it seems that the
connection pooling in activerecord in 2.1.x is fubar. Can somebody confirm
that for me please?
I've tried making the puppet master explicitly give up the connection
(disconnect) but that wouldn't fly; it'd result in "MySQL::Error - the mysql
server went away" type of errors.