MySQL Bugs: #30540: size misinterpreting for some packets

Bug #30540	size misinterpreting for some packets - max_allowed_packet
Submitted:	21 Aug 2007 19:04	Modified:	25 Dec 2007 16:41
Reporter:	Nelson Theves	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	5.1.20	OS:	Windows
Assigned to:		CPU Architecture:	Any

Description:
I'm using MySQL with Bugzilla (Mozilla's bug tracking system) and I found a problem when attaching a especific file (AL3406.pb) to database.

The value of 'max_allowed_packet' is set to 1M.
The size of the AL3406.pb is 642KB.
I tried to attach another BMP file, 3Kb greater than AL3406.pb, and was possible.

A complete description of the problem can be found on this link:
https://bugzilla.mozilla.org/show_bug.cgi?id=392926

How to repeat:
Set 'max_allowed_packet' to 1M and then try to add the uncompressed file AL3406.pb to the database.

After changing 'max_allowed_packet' to 2M, it was possible to attach the file to database.

Thank you for the report.

But version 5.1.11 is quite old. Please upgrade to current version 5.1.20, try with it and say us result.

I updated to version 5.1.20 but the problem persists.

Please, try to repeat with a newer version, 5.1.20, and inform about the results.

I repeated the test with a newer version, 5.1.20, and the results was the same as version 5.1.11.

Sorry, I meant 5.1.21, NOT 5.1.20 as I had written...

Anyway, as 5.1.22 is already released, please, try to repeat with 5.1.22 and inform about the results.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".