Re: MySQLQueryInterruptedException while no one killed the query
Posted by: Todd Farmer
Date: October 06, 2014 11:11AM

Hi Nikolay,

The diagnostic query provided can be executed any time - it will tell you how many times a KILL command has been issued. There's no need to add it to Java code; executing from the command-line client is sufficient. There's also no need to execute it immediately following the error - it's a global counter, so we would expect to see it incremented if queries were killed since the last restart.

The timing you describe is strange, but I don't see this pointing towards internal Connector/Java defects. The code I've reviewed is very straight-forward: That Exception subclass is created only when triggered by very specific SQL State from the MySQL Server. I think it is highly improbable that this behavior originates entirely within Connector/Java.

Best regards,

Todd Farmer
MySQL @ Oracle

Options: ReplyQuote

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.