Re: Sending messages to queues - is my understanding correct

Thanks for clearing that up in a nice way. On Fri, Dec 2, 2016 at 8:31 PM, Gordon Sim wrote: > On 02/12/16 20:14, James Franco wrote: > >> I am trying to understand what happens when we send a message to a queue >> with a little more perspective. >> >> Supose I have an

Re: Sending messages to queues - is my understanding correct

On 02/12/16 20:14, James Franco wrote: I am trying to understand what happens when we send a message to a queue with a little more perspective. Supose I have an exchange called *my-ex *that has a queue called *my_q* and this queue is bound to the exchange with the binding key *my_bid*. Now

Sending messages to queues - is my understanding correct

I am trying to understand what happens when we send a message to a queue with a little more perspective. Supose I have an exchange called *my-ex *that has a queue called *my_q* and this queue is bound to the exchange with the binding key *my_bid*. Now when I send a message to the queue directrly

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

Hi Gordon, Thank you for your response. Believe I was able to figure out the problem as it was a race condition where a queue is deleted from the broker, but another thread attempts a close or retrieval operation on that JMS MessageConsumer. Solution was to synchronize on the JMS MessageConsumer.

Re: How to reference a default exchange - spout fails

On 02/12/16 00:53, James Franco wrote: My question is how can I access a default exchnage , say if I wanted to do something like this ./spout ' '/test_queue SOME_TEST_CONTENT File "./spout", line 101, in snd = ssn.sender(addr) File "", line 6, in sender File

Re: Qpid JMS client JmsConnection.close() hangs

Thanks! I'll try that as soon as 0.20.0 is released! This might also help with another issue I'm experiencing - The ThreadPoolExecutor in JmsConnection is producing non-daemon threads intentionally (I can see the comment, but still don't get the reason why to do it in your code.) Which means in