How to reference a default exchange - spout fails

I created a queue using the command: >> ./qpid-config add queue test_queue Then I get something like this ./qpid-config exchanges -r *Exchange '' (direct)bind [bd2dfd48-6f3f-4807-b591-df543a306403:0.0] => bd2dfd48-6f3f-4807-b591-df543a306403:0.0bind [qservice_queue] => qservice_queue

Re: Understanding Topics and Queues association with Exchanges

Ok that makes sense thanks for clearing that up On Thu, Dec 1, 2016 at 11:24 PM, Rob Godfrey wrote: > On Fri, 2 Dec 2016 at 00:01, James Franco wrote: > > > yes it is the qpid hello world example . In your statement > > > > "The binding used

Re: Understanding Topics and Queues association with Exchanges

On Fri, 2 Dec 2016 at 00:01, James Franco wrote: > yes it is the qpid hello world example . In your statement > > "The binding used depends on the topic type (which the client determines by > asking the broker) and the subject (or other details of the address). Since > no

Re: Understanding Topics and Queues association with Exchanges

yes it is the qpid hello world example . In your statement "The binding used depends on the topic type (which the client determines by asking the broker) and the subject (or other details of the address). Since no 'subject' is specified by default in hello world, and the exchange type is a

Re: I'm using the Qpid Broker and JMS MessageConsumer times out waiting for a sync

On 01/12/16 20:16, Michael Nachmias wrote: We are using the C++ Broker version 1.35.0. There is an error at the same time the sync timed out on the Broker: Nov 29 19:37:23 dc-mb-01 qpidd[902]: 2016-11-29 19:37:23 [Broker] error Execution exception: not-found: Unknown destination 192

Re: Understanding Topics and Queues association with Exchanges

On 01/12/16 20:18, James Franco wrote: Thanks for the reply Gordon , so another question that I had regarding the same topic was about the hello world example and how it is functioning ? In that example , we have a message producer and a consumer the producer sends a message to the default topic

Re: Understanding Topics and Queues association with Exchanges

Thanks for the reply Gordon , so another question that I had regarding the same topic was about the hello world example and how it is functioning ? In that example , we have a message producer and a consumer the producer sends a message to the default topic exchange amq.topic . Now I am confused

Re: I'm using the Qpid Broker and JMS MessageConsumer times out waiting for a sync

Hi Rob, We are using the C++ Broker version 1.35.0. There is an error at the same time the sync timed out on the Broker: Nov 29 19:37:23 dc-mb-01 qpidd[902]: 2016-11-29 19:37:23 [Broker] error Execution exception: not-found: Unknown destination 192

Understanding Topics and Queues association with Exchanges

I am trying to wrap my head around the association of topics and queues with an exchange. Here is my understanding so far (please correct me if I am wrong). In the end I have a question . Point 1: Whenever we create a queue by default it is under the default exchange amq.direct.We can move this

[HEADS UP] qpid-cpp 1.36.0, proton 0.16.0

Hi folks, It has been a few months since qpid-cpp 1.35.0 went out and there have been a number of improvements and fixes made since, so I think it would be good to do a qpid-cpp 1.36.0 release soon to go with proton 0.16.0. As an update on 0.16.0 itself, I'll be looking to make cut of that

Re: [Qpid Java Broker] Remove Derby jar causes broker to crash when creating a VritualHost with Derby message store or config

OK - changed under QPID-7561 -- Rob On 1 December 2016 at 17:04, Rob Godfrey wrote: > Yeah - using the same mechanism as BDB would mean that you wouldn't be > able to create a Derby vhost / vhostnode if the library

Re: I'm using the Qpid Broker and JMS MessageConsumer times out waiting for a sync

Hi Michael, Which Broker (Java/C++) are you using? Is there anything in the broker logs indicating an issue at the time where these errors are occurring? -- Rob On 1 December 2016 at 17:22, Michael Nachmias wrote: > Hello, > > I'm running a enterprise Java web

I'm using the Qpid Broker and JMS MessageConsumer times out waiting for a sync

Hello, I'm running a enterprise Java web application using Java jdk 1.7.0.101, Qpid 0.30, and JMS 1.1. I'm running into intermittent issues where closing or retrieving from the JMS MessageConsumer times out waiting for a sync. The following is the stack trace of the exception: 2016-11-29

Re: [Qpid Java Broker] Remove Derby jar causes broker to crash when creating a VritualHost with Derby message store or config

Yeah - using the same mechanism as BDB would mean that you wouldn't be able to create a Derby vhost / vhostnode if the library wasn't present... We basically add a check on startup in the class to see if the necessary preconditions for creating an object of the type are met. At that point you'll

Re: [Qpid Java Broker] Remove Derby jar causes broker to crash when creating a VritualHost with Derby message store or config

Hello Rob, Having the same behavior as BerkleyDB is enough for me right now. I don't mind the broker not starting if a VirtualHostNode is missing jars. However, I don't like the fact that a management operation can make a running broker fail especially when you have a lot of messages being

Re: Qpid JMS client JmsConnection.close() hangs

Close timeout handling has been fixed up a fair bit with issue: https://issues.apache.org/jira/browse/QPIDJMS-228 On 11/25/2016 11:04 AM, Robbie Gemmell wrote: "I also think I see an issue with the closeTimeout handling in that in one place it seems likely to be using the requestTimeout value

Re: [Qpid Java Broker] Remove Derby jar causes broker to crash when creating a VritualHost with Derby message store or config

Just to be clear - the current behaviour of the broker when started with a BDB VirtualHost*Node* and the BDB jar missing is for the broker to fail to start. A JSON vitualhostnode with a BDB virtualhost will allow the boker to start up, but the virtualhostnode will be in the ERROR state. It would

DSCP tags

Hello, do Proton client libraries support DSCP tagging of IP packets? I found the "transport.trafficClass" configuration option in qpid-jms, but I did not find anything similar in Proton C, C++, Python or Java API. Regards, Pavel -- View this message in context:

[Qpid Java Broker] Remove Derby jar causes broker to crash when creating a VritualHost with Derby message store or config

Hello, For legal issues, we are unable to ship Derby in our product. So to be able to use Qpid, I have removed the Derby jar and relaunched the broker which had a "Memory" virtual host. I tried to add a new VirtualHostNode/VirtualHost with config and message store "DERBY" and it crashed. I