stumbleupon/asynchbase — Issue #15: apparent multiput wire protocol incompatibility with 0.92.0-rc4
Author: b0b0b0b
Created: 2012-01-19 18:14:52+00:00
State: open

An OOME is caused in the receiving HBase server. I captured the following byte array at the receiving end:

[0, 0, 0, -67, 0, 0, 0, 28, 1, 0, 8, 109, 117, 108, 116, 105, 80, 117, 116, 0, 0, 0, 0, 0, 0, 0, 29, 1, 0, 0, 0, 0, 0, 0, 1, 57, 57, 0, 0, 0, 0, 53, 116, 115, 100, 98, 44, 44, 49, 51, 50, 54, 57, 51, 56, 48, 51, 51, 50, 50, 49, 46, 50, 48, 56, 56, 50, 51, 50, 101, 54, 98, 99, 48, 100, 57, 48, 55, 97, 55, 97, 101, 52, 50, 101, 99, 50, 51, 99, 101, 49, 102, 54, 55, 46, 0, 0, 0, 1, 1, 13, 0, 4, 1, 0, 18, -55, 96, 0, 0, 2, 0, 0, 4, 127, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, 0, 0, 0, 0, 1, 1, 116, 0, 0, 0, 1, 0, 0, 0, 48, 0, 0, 0, 44, 0, 0, 0, 28, 0, 0, 0, 8, 0, 13, 0, 4, 1, 0, 18, -55, 96, 0, 0, 2, 0, 0, 4, 1, 116, 2, 39, 127, -1, -1, -1, -1, -1, -1, -1, 4, 0, 0, 0, 0, 0, 0, 0, 12, 0, 0, 0, 0]

The cause of death is Array.newInstance with an array length somewhere over 900 million (it appeared to have decoded the array length from within the "multiPut" magic token).