[ https://issues.apache.org/jira/browse/PROTON-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14647483#comment-14647483 ]
ASF subversion and git services commented on PROTON-966: -------------------------------------------------------- Commit 77fa91e9cdbc640ffd67d331d3553d3e5060865e in qpid-proton's branch refs/heads/master from Robert Gemmell [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=77fa91e ] PROTON-966, PROTON-967: add EmptyFrame body and pass to frame handler like any other. Utilise this to make empty frame logging/tracing actually say Empty Frame instead of just null. > [proton-j] empty frames are logged/traced when sent but not when received > ------------------------------------------------------------------------- > > Key: PROTON-966 > URL: https://issues.apache.org/jira/browse/PROTON-966 > Project: Qpid Proton > Issue Type: Bug > Components: proton-j > Affects Versions: 0.9.1 > Reporter: Robbie Gemmell > Assignee: Robbie Gemmell > Fix For: 0.10 > > > Proton-j logs/traces empty frames when sent but does not when they are > received. This makes ascertaining idle timeout behaviour (which can use empty > frames) harder to debug. > The reason for this disparity is that the empty frames are swallowed by the > FrameParser rather than a null frame body being passed to its FrameHandler. > To resolve this, an EmptyFrame type can be introduced that can be processed > as a NOOP and logged/traced in the same fashion as other frames. -- This message was sent by Atlassian JIRA (v6.3.4#6332)