Unable to listen to topic subscriptions with the same name

Hi. I am experiencing some unexpected behavior and I was wondering if anyone here can shed some light on it. I have a sample application that can show what I'm talking about. It can be accessed at this github repo (the multipleTopics

[RESULT] [VOTE] Release Apache Qpid Broker-J 7.0.6

There were 5 binding +1 votes and no other votes received. The vote has passed. The voting thread can be found here: https://lists.apache.org/thread.html/ea246ffef25ceb7c38a1eb90230e8e567502b6e80b493814e2514880@%3Cusers.qpid.apache.org%3E I will add the archives to the dist release repo and rele

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

Hi Robbie, Thanks a lot for reply and detail explanation. I went through "http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-messaging-v1.0.html#section-message-format"; and understood that there could be the infrastructure property as well. Some Difference between AMQP and JMS standard 1. A

Re: [Broker-J 7.0.3] Memory configuration store and messages recovery

Sure - but at that point you really need to provide the vhost config before the vhost itself starts up... would providing all the config (including the queue UUIDs) in a virtualHostInitialConfiguration provided to the VirtualHostNode on creation help I wonder... -- Rob On Fri, 22 Jun 2018 at 12:1

RE: [Broker-J 7.0.3] Memory configuration store and messages recovery

Hello Rob, The main problem is to keep my version of the config in sync with the one of each broker. And knowing that all our brokers have the same config the added complexity seems a bit overkill. Especially when you start thinking about broker restart, scale up, scale down... Olivier -Or

Re: [Broker-J 7.0.3] Memory configuration store and messages recovery

In general, in order to be able to recover the queues from a message store, the broker needs to know details of the queue - not only its name, but also the type of the queue (standard, priority, LVQ, etc) as well as other queue properties... this is precisely the data which is stored in the configu

RE: [Broker-J 7.0.3] Memory configuration store and messages recovery

Hello Keith, Thanks for the quick answer. Our target is a cluster of brokers and dispatch-routers. To configure it we created a management component that centralizes the configuration of all the Qpid components. With this approach, having the broker store its own configuration is redundant with

Re: [Broker-J 7.0.3] Memory configuration store and messages recovery

Hello Olivier Let me say first that the memory store's primary use-case is to aid development and testing of Broker-J, by speeding ups the test cycle. It also has utility when using embedding Broker-J in the unit tests of another project and you want to discard all messaging state between tests.

[Broker-J 7.0.3] Memory configuration store and messages recovery

Hello, I was running some tests on a Java Broker with 'Memory' configuration store and 'DERBY' message store. Is there a way with this configuration to recover the messages stored in DB upon a broker restart? Because it looks like the messages are mapped to the queue UUID and that they are disc