Hi Kathey, > I am working on an issue where the following exception occured after a > long 16hr stress run.
Another possibility is that this could be DERBY-428, which has a very similar "signature". > I suppose it > could be offset for bytes, but the ensurelength(4) seems like it should > take care of that. That ensurelength() call is exactly the fix to DERBY-428, so it's worth verifying that your environment is running with this fix. thanks, bryan
