Wrong Handling Of EOF Packet In Relation To Connector/J And MySQL 5.7

(Doc ID 2250081.1)

Last updated on JULY 30, 2017

Applies to:

MySQL Connectors - Version 5.1 and later
Information in this document applies to any platform.


On : 5.1 version, Connector/J and JDBC

Packet 6: The Deprecate-EOF flag is set by server and client
Packet 24: Query 1
Packet 25: Response as expected
Packet 28: Query 2
Packet 29: Wrong result: "05 00 00 03 fe 00 00 02 00" is an EOF packet
Note that all queries are over one connection.

 The expectation is that 0x00 is used to indicate an EOF packet and not the old 0xFE

The issue can be reproduced at will with the following steps:
1. Use and earlier version such as 5.1.38
2. Peform the same queries and do a packet capture
3. Compare EOF packets

The issue has the following business impact:
Due to this issue, users cannot understand why this is happening and how it will affect their application.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms