Do you have sample data that triggers this?
From the stacktrace, it looks like you have an embedded message that misreported its size.
When the string field of that embedded message is parsed, the string length could not fit within the size of its container (the embedded message)
Its not really 100% since if a message is mis-encoded/decoded, any error can popup.
It could be the gzip decoding that could be the culprit (or the other parts of your stack).
You could test the same data without the extra layers to see if protostuff is the culprit here.
I've gotten some few reports before and it came down to the other parts of their stack being the culprit.
--
When the cat is away, the mouse is alone.
- David Yu