Bug #59959 small values of --max-allowed-packet are not being honored

Submitted:	5 Feb 2011 0:51	Modified:	26 Apr 2011 15:20
Reporter:	Shawn Green	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: General	Severity:	S2 (Serious)
Version:	5.1.49	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
The MySQL command line client can send commands larger than the max_allowed_packet value and they are not being rejected. 

The test case below clearly shows that the max_allowed_packet value was set and that I was able to execute a command much larger than the indicated value. 

max_allowed_packet is a protective setting. If it is failing, then this could be serious. 

How to repeat:
Too large to post in this field. See attached test case.

Suggested fix:
Respect the max_allowed_packet limit or update the manual to indicate when it is ignored.

A session log indicating the failure of max_allowed_packet to reject a command that was too large

Attachment: bug59959_testcase.txt (text/plain), 11.76 KiB.

Noted in 5.1.57, 5.5.12, 5.6.3 changelogs.

The server permitted max_allowed_packet to be set lower than 
net_buffer_length, which does not make sense because
max_allowed_packet is the upper limit on net_buffer_length values.
Now a warning occurs and the value remains unchanged. 

CHANGESET - http://lists.mysql.com/commits/134032

Page generated in 0.051 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
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.