Bug #69777 Setting maxAllowedPacket below 8203 makes blobSendChunkSize negative
Submitted: 18 Jul 2013 11:40 Modified: 25 Nov 2013 19:44
Reporter: Filipe Silva Email Updates:
Status: Closed Impact on me:
Category:Connector / J Severity:S3 (Non-critical)
Version:5.1.25 OS:Any
Assigned to: Filipe Silva CPU Architecture:Any

[18 Jul 2013 11:40] Filipe Silva
When setting the property maxAllowedPacket with a value below 8203 in the connection string, causes a negative value in the property blobSendChunkSize.

This seems not to be an expected behaviour, however, the effect by having a negative value in blobSendChunkSize should be tested.

This bug could be somehow related to Bug#10859.


How to repeat:
Create a connection with property maxAllowedPacket below 8203, get blobSendChunkSize property value.

Test case attached.
[18 Jul 2013 11:40] Filipe Silva
test case

Attachment: ConnPropBlobSendChunkSizeNegative.java (text/x-java), 719 bytes.

[25 Nov 2013 19:44] Daniel So
Added the following entry to the Connector/J 5.1.28 changelog: 

"A validation is added to check if blobSendChunkSize is negative (which is the case when maxAllowedPacket is set with a value less than or equal to “8203”) when useServerPrepStmts=true. It throws an exception when the validation fails."