[QPIDJMS-80] Failure to send messages to both Azure and Windows Service Bus

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.3.0
• Component/s: qpid-jms-client

Environment

Windows 8.1 client Windows Service Bus 1.1 and Azure Cloud Service Bus Queue

• Assignee: Robbie Gemmell
• Reporter: Andrew Cartwright
• Created: 28/Jun/15 12:21
• Updated: 06/Jan/16 12:32
• Resolved: 09/Jul/15 16:19

Description

A test harness written to send a number of messages to a queue works fine against the Qpid Java Broker 0.32 but with Azure and Windows Service Bus even though connection is established and the link is opened messages are never delivered.
From my investigation and a comparison of the output from the Qpid JMS that ships in the 0.32 build there is an issue with the Begin performative in Proton-J 0.9.1 where the incoming and outgoing windows are set to 0.
A change to org.apache.qpid.proton.engine.impl.TransportSession.java in my test environment resulted in successful deliver of messages to all three brokers when both windows were initialised to 2048.

Issue Links

• is part of: QPIDJMS-84 update proton-j dependency to 0.10
• relates to: PROTON-936 update session outgoing window handling
• relates to: PROTON-940 provide the session initial incoming window via Begin rather than sending a separate Flow