[PROTON-966] [proton-j] empty frames are logged/traced when sent but not when received

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: proton-0.9.1
• Fix Version/s: proton-0.10
• Component/s: proton-j
• Assignee: Robbie Gemmell
• Reporter: Robbie Gemmell
• Created: 30/Jul/15 10:55
• Updated: 07/Jan/16 12:14
• Resolved: 30/Jul/15 11:16

Description

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.

Issue Links

• is depended upon by: QPIDJMS-90 Received empty frames are not logged
• relates to: PROTON-967 [proton-j] make empty frame logging actually mention that it is an empty frame.