Bug #69452 | memory size connection property doesn't support large values well | ||
---|---|---|---|
Submitted: | 12 Jun 2013 15:53 | Modified: | 23 Oct 2013 15:48 |
Reporter: | Jess Balint | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / J | Severity: | S3 (Non-critical) |
Version: | 5.1 | OS: | Any |
Assigned to: | Filipe Silva | CPU Architecture: | Any |
[12 Jun 2013 15:53]
Jess Balint
[12 Jun 2013 15:54]
Jess Balint
test case
Attachment: MemorySizeParsingBug.java (text/x-java), 666 bytes.
[12 Jun 2013 15:55]
Jess Balint
expected output: locatorFetchBufferSize is 2147483648 locatorFetchBufferSize is 1073741824
[23 Oct 2013 15:48]
Daniel So
Added the following entry to the Connector/J 5.1.27 changelog: When setting a connection property with a value for blobSendChuckSize, largeRowSizeThreshold, or locatorFetchBufferSize, the suffix “G” was not recognized and caused an error to be thrown. With this fix, Connector/J now supports using “GB” for gigabyte for the purpose.