MySQL Forums
Forum List  »  Connector/JDBC and Java

Connector/MXJ not shutting down on Windows shutdown?
Posted by: Don Bisdorf
Date: February 27, 2013 01:03PM

I know that Connector/MXJ is end-of-life; however, I'm hoping someone on the forums might be able to answer a question for me.

We have an applicaton that's using MySQL Community Edition 5.5.9 and MySQL Connector/MXJ version 5.0.12. We use Connector/MXJ to start up and shut down the MySQL server. Our Java app has a shutdown hook registered so that we can call MysqldResource.shutdown() if our app is terminated. However, we are frequently noticing that if a user shuts down Windows without shutting our app down first, that we get stderr output similar to the following the next time we start MySQL:

130227 10:33:42 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Last MySQL binlog file position 0 1096, file name .\binary-log.000003
130227 10:33:44 InnoDB: Waiting for the background threads to start
130227 10:33:45 InnoDB: 1.1.5 started; log sequence number 12184427
130227 10:33:45 [Note] Recovering after a crash using binary-log
130227 10:33:45 [Note] Starting crash recovery...
130227 10:33:45 [Note] Crash recovery finished

In my web searches for this issue, I was able to find only this seven-year old mailing list post that seems to directly address our situation:

Can anyone tell me if the latest version of Connector/MXJ still has a problem shutting down cleanly under Windows? Also, this old mailing list post seems to suggest that these messages are harmless and that the situation will not result in data loss; is this still accurate?

Any assistance would be appreciated.


Options: ReplyQuote

Written By
Connector/MXJ not shutting down on Windows shutdown?
February 27, 2013 01:03PM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.