#362 ✓resolved
Nathan Herald

Database connection is lost forever

Reported by Nathan Herald | June 10th, 2008 @ 10:59 AM

DM no longer reconnects to a DB after the connection is lost.

With the old way things worked, if the DB was lost it would error but would then immediately reconnect so the next DB call worked. Now it stays disconnected and all DB calls thereafter fail.

Comments and changes to this ticket

  • Sam Smoot

    Sam Smoot June 10th, 2008 @ 10:08 PM

    Connections are scavenged now, so this should be much less of an issue.

    I'll keep this open until I add flushing to the object-pooling though, and tweak the DataObjectsAdapter to flush the pool on error.

  • Jonathan Stott (namelessjon)

    Jonathan Stott (namelessjon) November 30th, 2008 @ 07:48 AM

    • Assigned user changed from “Sam Smoot” to “ssmoot (at gmail)”
    • State changed from “new” to “hold”

    Placing a hold on this til I hear back from ssmoot about if those tweaks were ever made.

  • Dan Kubb (dkubb)

    Dan Kubb (dkubb) December 5th, 2008 @ 12:12 AM

    • Assigned user changed from “ssmoot (at gmail)” to “Dirkjan Bussink”

    Dirkjan, I know Jon sent this to Sam for comment, but since he's really busy this week I was wondering if you wouldn't mind looking at the code to see if Sam's finished the tweaks he mentioned in the above comment?

    Also, is this at all related to the issue with do_mysql where it drops connections on any error? If there was an error where the connection was dropped (not related to the one where it does so explicitly) would it reconnect automatically, or would the error bubble up to the application?

    Should the behavior be that if the connection drops (for any reason) that it reconnects automatically, or should an exception be thrown?

  • Dirkjan Bussink

    Dirkjan Bussink December 5th, 2008 @ 03:25 AM

    • State changed from “hold” to “resolved”

    Afaik I've added reconnection support to both do_mysql and do_postgres. I've asked people who filed those specific tickets for testing whether it works for them now. I'm marking this as resolved now, if there are still issues, we should reopen.

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

People watching this ticket