Bug #77776 Got a packet bigger than 'max_allowed_packet' not shown if packet >= 4M

• Submitted: 18 Jul 2015 19:19
• Modified: 20 Jul 2015 9:54
• Reporter: Daniël van Eeden (OCA)
• Status: Verified
• Category: Connector / Python
• Severity: S3 (Non-critical)
• Version: 2.0.4, 1.1.6, 2.1.3
• OS: Any
• CPU Architecture: Any

[18 Jul 2015 19:19] Daniël van Eeden

Description:
With MySQL 5.6.35 with a 1M max_allowed_packet:
SET GLOBAL max_allowed_packet=1*1024*1024;

If I insert something < 4 MiB:
mysql.connector.errors.OperationalError: 1153 (08S01): Got a packet bigger than 'max_allowed_packet' bytes

If I insert something >= 4 MiB:
mysql.connector.errors.OperationalError: 2055: Lost connection to MySQL server at '::1:5625', system error: 32 Broken pipe

Wireshark shows that the server does send the max_allowed_packet back.

There is a 1-byte difference in the maximum size for the payload between versions:
4049259 1.1.6
4049258 2.0.4

How to repeat:
See description

[20 Jul 2015 9:54] MySQL Verification Team

Hello Daniël,

Thank you for the report.

Thanks,
Umesh