Bug #59941 | cluster/j - columns with varbinary(>255) fails | ||
---|---|---|---|
Submitted: | 4 Feb 2011 10:50 | Modified: | 31 Mar 2011 11:10 |
Reporter: | Johan Andersson | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Cluster: Cluster/J | Severity: | S3 (Non-critical) |
Version: | 7.1.9a | OS: | Any |
Assigned to: | Craig Russell | CPU Architecture: | Any |
Tags: | cluster, ClusterJ |
[4 Feb 2011 10:50]
Johan Andersson
[4 Feb 2011 22:18]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/130484 4083 Craig L Russell 2011-02-04 Bug #59941 VM crash invalid memory access with varbinary(256) column clusterj was incorrectly asking for the charset for a longvarbinary column.
[4 Feb 2011 23:54]
Craig Russell
The important part of the patch is the file storage/ndb/clusterj/clusterj-tie/src/main/java/com/mysql/clusterj/tie/ColumnImpl.java The others are test files.
[31 Mar 2011 11:10]
Jon Stephens
Documented fix in the NDB-7.1.12 changelog as follows: ClusterJ incorrectly asked for the character set for a LONGVARBINARY column with VARBINARY(256) columns, leading to a VM crash caused by invalid memory access. Closed.