Re: [VOTE] Release Apache Qpid Broker-J 7.0.6

Alex, There is a problem with .ascs in the 7.0.6-rc1 tree. They appear to contain a literal html response describing a 404 situation. svn cat https://dist.apache.org/repos/dist/dev/qpid/broker-j/7.0.6-rc1/apache-qpid-broker-j-7.0.6-src.tar.gz.asc | head -3 404 - Repository with

Re: [VOTE] Release Apache Qpid Broker-J 7.0.6

Hi folks, My apologies, I committed wrong files. I uploaded correct files. The issue should be fixed. Kind Regards, ALex On 20 June 2018 at 22:41, Keith W wrote: > Alex, > > There is a problem with .ascs in the 7.0.6-rc1 tree. They appear to > contain a literal html response describing a 404

Re: how to set ServiceBus Message properties like MessageID, ContentType, PartitionKey ?

Please find attached screenShot. -- Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html - To unsubscribe, e-mail:

how to set ServiceBus Message properties like MessageID, ContentType, PartitionKey ?

Hi Team, I am using "qpid-jms-client-0.33.0" and publishing message to ServiceBus. We have requirement to set service bus Message Properties like MessageID, ContentType, PartitionKey, CorrelationId, ReplyTo. I am able to set CorrelationId and ReplyTo but not able to set MessageID, ContentType

Question regarding support for consumer priority in competing consumer use-case

Hi QPid team, I have a question regarding the possibility to add a priority to consumers in a competing consumer use-case. I have a scenario where I have many consumers competing on a FIFO queue. These consumers interact with external resources which is expensive. As such I wish to optimise

Re: Question regarding support for consumer priority in competing consumer use-case

Hi Fergus, which of the Qpid components are you using / looking to use? For instance Qpid Broker-J does support different consumer priorities: https://qpid.apache.org/releases/qpid-broker-j-7.0.5/book/Java-Broker-Runtime-Consumers.html . -- Rob On Wed, 20 Jun 2018 at 11:57, fergus wrote: >

Clarification of behaviour using client acknowledge/accept mode

Hi Qpid team, I have scanned the documentation of the broker, proton and jms clients and havent' been able to clarify some aspects about the client acknowledge/accept modes. 1. When using a proton receiver with auto_accept=false, if the receiver does receives but does not accept/reject

Re: Clarification of behaviour using client acknowledge/accept mode

The clients wont accept/release/other the message on their own, so it will remain 'owned' by the consumer it was given to in general, until it goes away, then it could be delivered to another consumer. However, the specific end behaviour will also depend on the server you are using, and perhaps