[
https://issues.apache.org/jira/browse/QPIDJMS-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell resolved QPIDJMS-80.
-----------------------------------
Resolution: Fixed
Thanks for the update Andrew, the logs look good following the change. Some
folks from Microsoft were part of the discussions on the list and have
indicated they will also look to change the Service Bus behaviour as well in
future.
I've raised QPIDJMS-84 for the actual change, updating master to use the PRoton
0.10 snapshots for now ahead of the actual release (which should be soon
hopefully), so I'm closing this JIRA out now.
> Failure to send messages to both Azure and Windows Service Bus
> --------------------------------------------------------------
>
> Key: QPIDJMS-80
> URL: https://issues.apache.org/jira/browse/QPIDJMS-80
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
> Affects Versions: 0.3.0
> Environment: Windows 8.1 client Windows Service Bus 1.1 and Azure
> Cloud Service Bus Queue
> Reporter: Andrew Cartwright
> Assignee: Robbie Gemmell
> Attachments: AZUREqpidX-jms-0.log, QueueWriter.java, azure10msg.txt,
> qpid10msg.txt, qpidX-jms-0.log, qpidjmstest.zip
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
