Mailing-List: contact users-help@qpid.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@qpid.apache.org
Received-SPF: pass (nike.apache.org: domain of lhornung@choppertrading.com
 designates 38.98.162.199 as permitted sender)
From: Luba Hornung <lhornung@choppertrading.com>
To: "users@qpid.apache.org" <users@qpid.apache.org>
Date: Fri, 15 Jul 2011 09:16:29 -0500
Subject: RE: messages get resent after broker is restarted, C++
Thread-Topic: messages get resent after broker is restarted, C++
Thread-Index: AcxCzZH2GuhBPivaQ0W2Y3eMf4UmHwAK8R2Q
Message-ID: 
 <44AE62A7ED7A1F40AF0FC503B50F92780FDAEC2371@chopperexchange.choppertrading.com>
References: 
 <44AE62A7ED7A1F40AF0FC503B50F92780FDAEC22EB@chopperexchange.choppertrading.com>
 <4E20011B.5060105@redhat.com>
In-Reply-To: <4E20011B.5060105@redhat.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

So there is no way to set message Durability in the version 0.6 with messag=
ing API?
Client API has message.getDeliveryProperties().setTtl() but messaging/Messa=
ge.h does not have getDeliveryProperties() or setDurability() (mentioned in=
 the api help).

-----Original Message-----
From: Gordon Sim [mailto:gsim@redhat.com]
Sent: Friday, July 15, 2011 3:58 AM
To: users@qpid.apache.org
Subject: Re: messages get resent after broker is restarted, C++

On 07/15/2011 12:47 AM, Luba Hornung wrote:
> Why after qpid broker is restarted messages which had been received in a =
previous session get received again?
>
> 1)      I launch a broker, my server and a client.
>
> 2)      Server sends messages to clients.
>
> 3)      I disconnect broker by Ctrl+c
>
> 4)      My client and server wait until I restart the broker again.
>
> 5)      The messages that the server had sent in 2) are received by clien=
ts again.
>
> After a connection gets broken, I re-open the session and create new send=
ers and receivers with the same addresses.
> I am using C++ qpid version 0.6, messaging api.

The exactly-once mode is not yet supported; you will get at-least-once
instead which can result in duplicates.

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org


CONFIDENTIALITY WARNING: This email including any attachments may contain p=
rivileged or confidential information and is for the sole use of the intend=
ed recipient(s). Any unauthorized use or disclosure of this communication i=
s prohibited. This e-mail may also be subject to specific non-disclosure an=
d confidentiality provisions.  The information contained herein is the prop=
erty of Chopper Trading, LLC.  If you believe that you have received this e=
mail in error, please notify the sender immediately and delete it from your=
 system.

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org