[CONJ-132] Unimplemented exceptions from original mysql drivers Created: 2015-01-20  Updated: 2015-07-21  Resolved: 2015-07-21

Status: Closed
Project: MariaDB Connector/J
Component/s: Other
Affects Version/s: 1.1.6, 1.1.7, 1.1.8
Fix Version/s: 1.1.9

Type: Bug Priority: Major
Reporter: Lukas Raska Assignee: Diego Dupin
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Blocks
blocks CONJ-158 Tests fail with max_allowed packets =... Closed

 Description   

Current version of MariaDB client library doesn't output actual exceptions when query fails for some reason.

I've recently came across this issue, when with MariaDB the exception was

Caused by: java.sql.SQLNonTransientConnectionException: Could not send query: Broken pipe

With official MySQL driver the exception was
Caused by: com.mysql.jdbc.PacketTooBigException: Packet for query is too large (9028625 > 4194304). You can change this value on the server by setting the max_allowed_packet' variable.

Which outputs the actual issue and doesn't imitate network issue.

 Comments   
Comment by Vladislav Vaintroub [ 2015-01-20 ]

The network issue is not "imitated". The connection is closed for real, on the server side.
The driver sends the query, the server closes the connection, because packet is too large. (Different from ConnectorJ, this driver does not count bytes in packet it sends)

Comment by Diego Dupin [ 2015-07-21 ]

this issue has been solved in 1.1.9 with CONJ-158.
thrown error label is for example :
java.sql.SQLTransientException: Could not send query: max_allowed_packet exceeded. wrote 50331657, max_allowed_packet = 50331648

Generated at Thu Feb 08 03:13:24 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.