You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2016/02/12 19:18:18 UTC

[jira] [Created] (AMQ-6169) STOMP: Invliad frames are logged in warn messages

Timothy Bish created AMQ-6169:
---------------------------------

             Summary: STOMP: Invliad frames are logged in warn messages
                 Key: AMQ-6169
                 URL: https://issues.apache.org/jira/browse/AMQ-6169
             Project: ActiveMQ
          Issue Type: Bug
          Components: stomp
    Affects Versions: 5.13.1, 5.13.0, 5.12.1, 5.12.0
            Reporter: Timothy Bish
            Assignee: Timothy Bish
             Fix For: 5.14.0


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.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)