Hi all,
Every now and then, when I restart my qpidc broker (version 0.22) some messages
reappear in the queues, although they were long since taken from the queues
(and committed).
Something like that (qpid-stat output):
queue dur autoDel excl msg
Yes, they are independent.
Good luck,
-Steve
> -Original Message-
> From: Rajesh Khan [mailto:rajeshkhan...@gmail.com]
> Sent: Thursday, August 29, 2013 4:51 PM
> To: users@qpid.apache.org
> Subject: Re: Possibility Running multiple instances of broker on the same
> machine.
>
> Yeah I tr
Yeah I tried this
C:\qpid-0.18\qpid-0.18\cpp\src\Release>qpidd --tcp-nodelay --auth=no
--port=5677
--data-dir=QPIDDEVENTORDER.DATA
and it works. So both of them are totally independant of each other now am
I correct ?
On Thu, Aug 29, 2013 at 4:48 PM, Steve Huston wrote:
> Yes, you'll need a
Yes, you'll need a separate data directory. I apologize for leaving that out.
> -Original Message-
> From: Rajesh Khan [mailto:rajeshkhan...@gmail.com]
> Sent: Thursday, August 29, 2013 4:45 PM
> To: users@qpid.apache.org
> Subject: Re: Possibility Running multiple instances of broker on t
On Thu, Aug 29, 2013 at 04:37:25PM -0400, Rajesh Khan wrote:
> We are currently running a C++ broker on our windows 7 machine using the
> following command:
>
> *qpidd --tcp-nodelay --auth=no*
>
> I wanted to know if it will be possible to launch another instance of the
> broker on the same machi
Thank you for your reply Steve. I tried doing that and I get the following
response:
C:\qpid-0.18\qpid-0.18\cpp\src\Release>qpidd --tcp-nodelay --auth=no
--port=5677
2013-08-29 16:44:18 [Broker] critical Unexpected error:
\TEMP\QPIDD.DATA/lock: T
he process cannot access the file because another
Add the --port= option to specify a new port.
> -Original Message-
> From: Rajesh Khan [mailto:rajeshkhan...@gmail.com]
> Sent: Thursday, August 29, 2013 4:37 PM
> To: users@qpid.apache.org
> Subject: Possibility Running multiple instances of broker on the same
> machine.
>
> We are curre
We are currently running a C++ broker on our windows 7 machine using the
following command:
*qpidd --tcp-nodelay --auth=no*
I wanted to know if it will be possible to launch another instance of the
broker on the same machine. I believe we will have to give it a different
port to bind on but then
On 08/29/2013 03:00 PM, Jakub Scholz wrote:
Right now, it seems that the reconnect(...) method always requires the URL
of the broker to reconnect to. Maybe it would be useful to also add a
reconnect() method without the URL parameter, to trigger the reconnect
based on the URL which was specified
Hi Gordon,
That definitely looks like a very nice feature. There are many situations
when you want to trigger the reconnect manually and not leave it fully on
the client library.
Right now, it seems that the reconnect(...) method always requires the URL
of the broker to reconnect to. Maybe it wou
On 08/28/2013 11:50 PM, Rajesh Khan wrote:
Thanks that seems to do the trick. Any idea how I could do it
programatically .
Attached is a simple example program. However I would advise
investigating the autodelete issue a little more as I'm fairly confident
it will do as expected if used in t
On 08/28/2013 09:53 PM, Rajesh Khan wrote:
I wanted to know what my options are when I need to clear up queues.
My first preference would be to clear them up programatically. I tried
setting a queue to auto-delete however that does not seem to work.I have a
sender and a receiver. The receiver cre
On 08/29/2013 06:19 AM, Jeremy Wagner wrote:
Does a copy of a connection still share the same underlying pointer? How about
through the assignment operator? Thanks!
Yes, Connections, Sessions, Senders and Receivers are all 'Handles',
which essentially has a smart pointer to the actual state.
13 matches
Mail list logo
