You are viewing a plain text version of this content. The canonical link for it is here.
Posted to proton@qpid.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2015/07/30 13:17:04 UTC
[jira] [Resolved] (PROTON-966) [proton-j] empty frames are
logged/traced when sent but not when received
[ https://issues.apache.org/jira/browse/PROTON-966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell resolved PROTON-966.
-----------------------------------
Resolution: Fixed
> [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)