Details
Major Description
When the STOMP protocol converter encounters a frame that is badly encoded it logs out a warning that prints the entire frame contents in the warn message. This leads to some confusing results or logs of 'null' as the decoder never got to creating a full frame instance before failing.
If the frame happens to get read but contains corrupted data the log can get spammed with garbage characters and becomes somewhat unreadable.
We should not log the frame if there is one at warn level, perhaps allow for trace logging it. We could attempt to log the frame Action if one was read and is valid but otherwise should not pollute the logs with entire frames.