Perl Debugger: DBD::mysql::db do failed: MySQL server has gone away at

Question

I use MySQL with the DBI Module for my perl programming database connections. I got the error message as below when using mysql :

Issuing rollback() due to DESTROY without explicit disconnect() of       
DBD::mysql::db handle db=db;ip=X.X.X.X; at /code/save2db.plx line 104.
DBD::mysql::db DESTROY failed: MySQL server has gone away at   
/code/save2db.plx line 104.
    (in cleanup) DBD::mysql::db DESTROY failed: MySQL server has gone away  
at /code/save2db.plx line 104.

the line 104 in my code is

103    $dbh->disconnect;
104    exit;

Any idea why this happens? I'd appreciate any feedback.

pii_ke · Accepted Answer · 2017-12-05 08:01:45Z

1

The transaction behaviour of the disconnect method is, sadly, undefined. Some database systems (such as Oracle and Ingres) will automatically commit any outstanding changes, but others (such as Informix) will rollback any outstanding changes. Applications not using AutoCommit should explicitly call commit or rollback before calling disconnect.

See https://metacpan.org/pod/DBI#disconnect

answered Dec 5, 2017 at 8:01

pii_ke

2,9112 gold badges22 silver badges31 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

georgetovrea Over a year ago

but in my script , I have add $dbh->do("COMMIT") or die "$dbh->errstr"; before disconnect

pii_ke Over a year ago

can you try using begin_work, commit and rollback methods for transaction management, instead of doing them with raw SQL?

Collectives™ on Stack Overflow

Perl Debugger: DBD::mysql::db do failed: MySQL server has gone away at

1 Answer 1

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related