Thank you. Will keep that in mind.
Nitin
-Original Message-
From: Gordon Sim [mailto:g...@redhat.com]
Sent: Thursday, December 04, 2014 4:20 AM
To: dev@qpid.apache.org
Subject: Re: Qpid question On High Priority messages
On 12/03/2014 06:25 PM, Nitin Shah wrote:
Is there a way in qpid
Hi,
Is there a way in qpid to send message at the highest priority such that it
can overtake current messages in transit. Perhaps there is a way to define a
high priority queue? We do not want to have a high bandwidth for it, but
messages should be able to take the highest priority.
Thanks
: Ted Ross [mailto:tr...@redhat.com]
Sent: Tuesday, October 28, 2014 12:37 PM
To: Nitin Shah; dev@qpid.apache.org
Subject: Re: Question On QPID behavior
Nitin,
What are your reliability requirements? Is your application
bandwidth-sensitive?
You are dealing with tradeoffs in reliability, message
reduces the number of message-IDs that needs to be stored for de-duplication.
I do believe that this capability will be appearing soon in the Proton API work
that Gordon Sim is doing in a branch currently.
-Ted
On 10/29/2014 09:38 AM, Nitin Shah wrote:
Hi Ted, Dev team
Thanks for the response
Did not get a response to this, so wondered if anyone can help with this.
Thanks
Nitin
-Original Message-
From: Nitin Shah
Sent: Monday, October 27, 2014 5:29 PM
To: dev@qpid.apache.org; tr...@redhat.com
Cc: Nitin Shah
Subject: RE: Question On QPID behavior
Hi Ted ,
Thanks for your
is the same although the documentation seems to indicate that once
acked to the broker, the messages should not be repeated.
Can I ask for some feedback and clarify this.
Thanks
Nitin Shah
. We are using the reliable connection option ( at least
once ).
Thanks
Nitin Shah
-Original Message-
From: Ted Ross [mailto:tr...@redhat.com]
Sent: Monday, October 27, 2014 4:26 PM
To: dev@qpid.apache.org
Subject: Re: Question On QPID behavior
Nitin,
One thing to keep in mind
__
From: Gordon Sim [g...@redhat.com]
Sent: Tuesday, April 08, 2014 4:50 AM
To: dev@qpid.apache.org
Subject: Re: Qpid and Behavior on NTP time change
On 04/03/2014 09:50 PM, Nitin Shah wrote:
Gordon , Qpid team,
Can you explain what that means.
Changing the time will confuse the broker
change
On 03/28/2014 02:50 PM, Nitin Shah wrote:
When TIME changed thru the CLI on the module that is running the broker , a
time Change time of a minute through CLI saw the following errors on primary
Module ( running the broker ) but no errors on the other modules.
2014-03-27T10:38:34.919457
...@redhat.com]
Sent: Wednesday, March 26, 2014 12:52 PM
To: dev@qpid.apache.org
Subject: Re: Qpid and Behavior on NTP time change
On 03/25/2014 06:55 PM, Nitin Shah wrote:
Hi ,
I have talked to this mailing list before as we are users of QPID in our
distributed system. Our architecture has
Hi Andrew and Qpid team,
We are really blocked by this issue and need to have a conversation going about
the options to resolve our issue. I am adding others from our team so they can
chime in if necessary.
Thanks
Nitin
-Original Message-
From: Nitin Shah
Sent: Tuesday, March 25
that depend on using the same time reference.
Any thoughts?
Nitin
-Original Message-
From: Nitin Shah [mailto:ns...@btisystems.com]
Sent: Wednesday, March 26, 2014 10:56 AM
To: Andrew Stitcher; dev@qpid.apache.org
Cc: Gordon Sim (g...@redhat.com); Atif Faheem; Tony Hart; Lynne
: Andrew Stitcher [mailto:astitc...@redhat.com]
Sent: Wednesday, March 26, 2014 11:20 AM
To: dev@qpid.apache.org
Cc: Gordon Sim (g...@redhat.com); Atif Faheem; Tony Hart; Lynne Morrison
Subject: Re: Qpid and Behavior on NTP time change
On Wed, 2014-03-26 at 10:56 -0400, Nitin Shah wrote:
Hi Andrew
My responses embedded below
-Original Message-
From: Gordon Sim [mailto:g...@redhat.com]
Sent: Wednesday, March 26, 2014 12:52 PM
To: dev@qpid.apache.org
Subject: Re: Qpid and Behavior on NTP time change
On 03/25/2014 06:55 PM, Nitin Shah wrote:
Hi ,
I have talked to this mailing
Hi ,
I have talked to this mailing list before as we are users of QPID in our
distributed system. Our architecture has multiple modules connected together
via a backplane Ethernet link. We use QPID version 0.24 release both broker and
clients are C++.
Recently we have been trying to
and that seems to cause the
lock up. If NTP does it , that seems fine.
Nitin
-Original Message-
From: Andrew Stitcher [mailto:astitc...@redhat.com]
Sent: Tuesday, March 25, 2014 4:26 PM
To: dev@qpid.apache.org
Cc: Nitin Shah; Gordon Sim (g...@redhat.com)
Subject: Re: Qpid and Behavior on NTP
Yes we are doing sender.close() . Also why does the broker replay messages?
Nitin
-Original Message-
From: Gordon Sim [mailto:g...@redhat.com]
Sent: Tuesday, November 12, 2013 5:32 AM
To: dev@qpid.apache.org
Subject: Re: Problem/Explanation ?
On 11/11/2013 08:38 PM, Nitin Shah wrote
Nitin Shah
58) 22656 total bytes from ::new in 354 separate allocations
/opt/atlas/kit/bin/StartEquipmentMgr (operator new(unsigned long)+0x65)
[0x0x9aa791]
lib/libqpidmessaging.so.2 (__gnu_cxx::new_allocatorvoid**::allocate(unsigned
long, void const*)+0x42) [0x0x7f1119659518]
/lib
Hi,
We are using release 0.24 of the C++ broker and client software and we see this
exception occur. Can someone explain what seems to be going wrong?
2013-10-07T14:58:46.041107+00:00 pld0104 qpidd[1616]: 2013-10-07 14:58:46
[Protocol] error Execution exception: resource-limit-exceeded:
reached. Did
you not expect that?
-Steve
-Original Message-
From: Nitin Shah [mailto:ns...@btisystems.com]
Sent: Tuesday, October 08, 2013 3:54 PM
To: dev@qpid.apache.org
Cc: Nitin Shah
Subject: Can someone explain what is going on here
Hi,
We are using release 0.24 of the C
-Original Message-
From: Nitin Shah [mailto:ns...@btisystems.com]
Sent: Tuesday, October 08, 2013 4:20 PM
To: dev@qpid.apache.org
Subject: RE: Can someone explain what is going on here
Is the limit saying that it has received a very large Message? The
size shown (
104857600
Hi Justin,
I would like to know if the actual release for 0.20 C++ broker and client has
happened? There was a lot activity of late, so I haven't kept up with
all the details.
Thanks
Nitin
-Original Message-
From: Justin Ross [mailto:jr...@apache.org]
Sent: Monday, February 04,
AM
To: dev@qpid.apache.org
Subject: Re: Broker repeating messages
On 10/08/2012 09:10 PM, Nitin Shah wrote:
We are running Qpid C++ broker(s) release version 0.18 . I find it
strange when the clients reconnect to a broker that has been killed
and restarted, messages get repeated. In my case
Hi,
Can someone answer what happens in Qpid C++ implementation version 0.18 when:
1. Having created a receiver and a thread is performing receives for all
receivers created using the getNextReceiver( ) with a timeout and at some point
later, another thread decides to close the receiver
Hi,
We are running Qpid C++ broker(s) release version 0.18 . I find it strange when
the clients reconnect to a broker that has been killed and restarted, messages
get repeated. In my case we set up the connection with the option =
reconnect:true. We also acknowledge the received messages as
Hi ,
I wanted to ask a question about whether this is allowed in the C++ Qpid
Broker/Client usage.
We wondered if one can use a single connection to the broker and have the same
session on that connection have one thread in a process send messages and have
another thread on the same process
You are welcome.
Nitin
-Original Message-
From: Alan Conway [mailto:acon...@redhat.com]
Sent: Monday, September 10, 2012 10:38 AM
To: dev@qpid.apache.org
Cc: Gordon Sim; Nitin Shah
Subject: RE: FW: problems starting the version 18 broker and its Crash
Thanks a lot for tracking
modules only directory
would verify that).
On 09/05/2012 04:48 PM, Nitin Shah wrote:
Ps if I run it in foreground then I get the following message
2012-09-05 11:39:45 [Broker] notice SASL disabled: No Authentication
Performed
2012-09-05 11:39:45 [Network] notice Listening on TCP/TCP6 port
Hi,
I tried to start the version 18 of the C++ broker and get the following error
in /var/log/messages and the broker dies. Any idea what we are doing wrong. We
have been using the version 16 and that starts fine.
10:29:35 nshah_1 qpidd[1550]: 2012-09-05 10:29:35 [Broker] notice SASL
On 08/15/2012 10:14 PM, Nitin Shah wrote:
Hi,
I wanted to run this by the developers to understand why this happens.
We are running the release 0.16 C++ broker and have written some
applications to use the infrastructure. I have developed a simple
applications that sends messages
...@redhat.com]
Sent: Tuesday, August 21, 2012 11:00 AM
To: dev@qpid.apache.org
Subject: Re: Can someone help to understand
On 08/21/2012 03:27 PM, Nitin Shah wrote:
I tried the suggestion you had. I found that the scenario still exists
and messages are repeated when the broker killed and restarted
My answers enclosed
From: Gordon Sim [g...@redhat.com]
Sent: Tuesday, August 21, 2012 11:52 AM
To: dev@qpid.apache.org
Subject: Re: Can someone help to understand
On 08/21/2012 04:21 PM, Nitin Shah wrote:
I did not specify a parameter to the sync call
Hi,
I wanted to run this by the developers to understand why this happens. We are
running the release 0.16 C++ broker and have written some applications to use
the infrastructure. I have developed a simple applications that sends messages
to a receiving application on from the amq.topic
We are using 0-16 (c++ brokers etc..) release. Does this affect backward
compatibility? We might not want to move to the next release unless there is no
impact on our implementations. Can someone comment and put me straight.
Thanks
Nitin
-Original Message-
From: Alan Conway
to allow you to specify **kwargs, but it looks like the
version that python is finding on your system is still the old one.
Andy
On Jun 6, 2012, at 8:29 AM, Nitin Shah wrote:
This is the message I had sent out 2 days ago. Can someone guide me .
I am running the 0-16 C_++ broker and issuing
This is the message I had sent out 2 days ago. Can someone guide me .
I am running the 0-16 C_++ broker and issuing this command gives this error.
Can someone point me to what is going on.
qpid-route link list
Failed: TypeError - addBroker() got an unexpected keyword argument
Hi Guys,
The version 0-16 of the tool qpid-route utility does not seem to work . I sent
the message out yesterday, but no one responded. I ran the version 0-14 of the
tools release against 0-16 broker and that seems to at least come back with a
reasonable answer. Can someone answer what action
I am running the 0-16 C_++ broker and issuing this command gives this error.
Can someone point me to what is going on.
qpid-route link list
Failed: TypeError - addBroker() got an unexpected keyword argument
'client_properties'
Thanks
Nitin
[cid:image001.png@01CD4273.DD68D640]
To: dev@qpid.apache.org
Subject: RE: Info
Hi Nitin,
1. No, different brokers would not automatically learn about each
other.
2. Correct, there is no broadcast/multicast taking place.
-Steve
From: Nitin Shah [mailto:ns...@btisystems.com]
Sent: Friday, May 11, 2012 4:41 PM
Hi ,
I am trying to understand and I cannot find the answer in any places I have
looked at. Can someone answer the following:
1. If we have a multiple card system and there are local qpidd C++
brokers that are to be run on each card. If each broker starts up
independently, do they find
Hi,
I wanted to understand where we stand on the release AMQP 1.0 vs. the current
broker implementation based on version 0-10 of the AMPQ standard. Are all
implementations proceeding to the 1.0 AMQP release standard and where can I
find out what the schedules are? I would like to use the
Never mind. I have it up and running
Nitin
[cid:image001.png@01CD2943.F7355E70]
From: Nitin Shah [mailto:ns...@btisystems.com]
Sent: Thursday, May 03, 2012 3:18 PM
To: dev@qpid.apache.org
Subject: Simple Question
Hi,
I would like to run the qpid-config etc calls from my login session. I
42 matches
Mail list logo