qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robbie Gemmell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPIDJMS-80) Failure to send messages to both Azure and Windows Service Bus
Date Wed, 08 Jul 2015 19:03:04 GMT

    [ https://issues.apache.org/jira/browse/QPIDJMS-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14619178#comment-14619178

Robbie Gemmell commented on QPIDJMS-80:

Hi Andrew,

We have been discussing the underlying issue on the mailing lists recently and I have prepared
some proton-j (and proton-c) changes based on that which will hopefully let things work with
ServiceBus as it currently behaves, plus a JMS client change to allow using a new config toggle
if ever needed.

I should get the changes in tomorrow morning UK time, but there are some other issues needing
resolved in the proton-j build at the moment that might get in the way of using them a little.
Given that and the fact we seem to be in opposing timezones, I have put up the binary archive
of a local build with the initial updates in case you are able to try it out before then.
You can find it at: http://people.apache.org/~robbie/qpid/jms/QPIDJMS-80/apache-qpid-jms-0.4.0-SNAPSHOT-bin.tar.gz

The quick summary is that the session outgoing window is now set to a very large fixed value
(which can be changed via the client using the URI option "amqp.sessionOutgoingWindow"), and
the incoming window is initialised earlier than previously. This is slightly different to
the change you mentioned making, but will give it similar behaviour at the initial point the
session is created so given the earlier change worked I'd expect this to behave similarly
but it would be good if you could try it out.


> 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,
> 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

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message