Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DESTROY failed: no connection #126

Open
dmr3 opened this issue Aug 15, 2024 · 0 comments
Open

DESTROY failed: no connection #126

dmr3 opened this issue Aug 15, 2024 · 0 comments

Comments

@dmr3
Copy link

dmr3 commented Aug 15, 2024

I am running Mojolicious services that use DBD::Pg through DBIx::Class or Mojo::Pg. Periodically, I see in the logs the following DBI exception a few times per day (difficult to reproduce):

(in cleanup) DBD::Pg::st DESTROY failed: no connection to the server

I found a silencing of the warning in the forking section of t/02attribs.t

local $SIG{__WARN__} = sub { warn $_[0] unless $_[0] =~ /DESTROY failed: no connection/ }; # shut up destroy warning

so this seems like the best place to ask about this DBI exception!

My services appear to churn along happily, reconnecting as needed. I checked and I am using AutoInactiveDestroy => 1 via DBI. I also run versions of the same services with connections to DBD::Oracle; there are no analogous exceptions coming through Oracle::DBD.

Would someone be able to provide more information about the exception and whether it can be avoided?

EDIT:
Perl v5.30.0
DBI::VERSION = 1.643
DBD::Pg::VERSION = 3.14.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant