What is the difference in the classes in qpid/client and qpid/messaging in C++?

2011-03-09 Thread Hickerson, David A
What is the difference between the classes in qpid/client and qpid/messaging in C++? I have noticed that Connection is in each. For a client application, which is supposed to be used? Some of the examples point to each and the documention seems to be more filled out for the messaging/ classes.

RE: Question about messaging::Address in the C++ code

2011-03-09 Thread Hickerson, David A
So if messaging::Address.name maps to a queue or topic. Does the messaging::Address.subject provide further refinement of messages sent to that queue or topic? -Original Message- From: Steve Huston [mailto:shus...@riverace.com] Sent: Wednesday, March 09, 2011 5:18 PM To: users@qpid.apac

RE: Question about messaging::Address in the C++ code

2011-03-09 Thread Steve Huston
Hi David, > I have been looking that the examples and the documentation > for messaging::Address. I am little confused as to what > messaging::Address.name (setName/getName) is. > > Is it a Session name, a URL for the broker, or something > completely different? Different. It's a queue or exc

Question about messaging::Address in the C++ code

2011-03-09 Thread Hickerson, David A
I have been looking that the examples and the documentation for messaging::Address. I am little confused as to what messaging::Address.name (setName/getName) is. Is it a Session name, a URL for the broker, or something completely different? Thanks, Dave David Hickerson

Re: onMessage() always acknowledges msg even if Session is set to CLIENT_ACK

2011-03-09 Thread Chris Sears
Hi Kim, Just to add to Rajith's comments, it sounds like you may be trying to use the ring queue, onMessage(), queue browsing and client acknowledgements in a way they were not designed to work. If you have multiple clients that all need to read the same message, the message producer should be se

Re: onMessage() always acknowledges msg even if Session is set to CLIENT_ACK

2011-03-09 Thread Rajith Attapattu
On Wed, Mar 9, 2011 at 2:47 PM, Kim Garcia wrote: > > Hi Rajith, > > It doesn't matter if the apps are consumers or queue browsers as long as > they share the messages (or get their own copy). > > I'm looking into using the javax.jms Topic object as suggested, but do the > messages have to be sen

Re: onMessage() always acknowledges msg even if Session is set to CLIENT_ACK

2011-03-09 Thread Rajith Attapattu
Just to follow up on this. I verified that if you don't ack the messages and once you close your session, the messages are then put back on the queue with the redelivered flag set. So another consumer will get it. Rajith On Mon, Mar 7, 2011 at 6:07 PM, Rajith Attapattu wrote: > Hi Kim, > > I ra

RE: onMessage() always acknowledges msg even if Session is set to CLIENT_ACK

2011-03-09 Thread Kim Garcia
Hi Rajith, It doesn't matter if the apps are consumers or queue browsers as long as they share the messages (or get their own copy). I'm looking into using the javax.jms Topic object as suggested, but do the messages have to be sent to a topic instead of a queue? If so, then that won't work

wierd error on connect

2011-03-09 Thread Matt Paul
Hi all, I'm having a somewhat strange error when trying to do a connect with a producer (using the client namespace): 2011-03-09 13:37:22 error Caught exception in state: 1 with event: 2: Operation not permitted (qpid/sys/posix/Socket.cpp:94) This is only occurring in 1 of the producers we've cr

Re: onMessage() always acknowledges msg even if Session is set to CLIENT_ACK

2011-03-09 Thread Rajith Attapattu
The answer below is assuming that all your apps are consumers and not queue browsers. If thats not the case then please let me know. Rajith On Wed, Mar 9, 2011 at 9:53 AM, Rajith Attapattu wrote: > Kim, > > If you want all the apps (consumers) on the same queue to get all the > messages in the

Re: onMessage() always acknowledges msg even if Session is set to CLIENT_ACK

2011-03-09 Thread Rajith Attapattu
Kim, If you want all the apps (consumers) on the same queue to get all the messages in the queue, then using 'Queues (as in JMS terms)' is not going to do it. As in a shared queue situation the messages will be distributed among them. Therefore you should use a Topic and all your consumers will