I moved the byte array size check to the constructor of SendByteArrayToNode allowing an app to fail gracefully if the limit is exceeded. Currently the check happens in the run method which has already been moved to another thread an thus cannot be caught by the existing "Object cannot be sent" log message.
I moved the byte array size check to the constructor of SendByteArrayToNode allowing an app to fail gracefully if the limit is exceeded. Currently the check happens in the run method which has already been moved to another thread an thus cannot be caught by the existing "Object cannot be sent" log message.