Mailing-List: contact users-help@qpid.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@qpid.apache.org
Message-ID: <DUB112-W5944D7A30B5977E22E5E40CD410@phx.gbl>
Content-Type: multipart/alternative;
	boundary="_0550c9d7-f636-4418-847f-7c0bc8911630_"
From: Adel Boutros <adelboutros@live.com>
To: "users@qpid.apache.org" <users@qpid.apache.org>
Subject: RE: [Proton-c] Random value of idle timeout causing error when
 below 1000
Date: Thu, 26 May 2016 10:19:51 +0200
Importance: Normal
In-Reply-To: <5745686C.2030207@redhat.com>
References: 
 <DUB112-W1121AE03E7466C875638F3CD400@phx.gbl>,<5745686C.2030207@redhat.com>
MIME-Version: 1.0
archived-at: Thu, 26 May 2016 08:20:09 -0000

--_0550c9d7-f636-4418-847f-7c0bc8911630_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello Gordon=2C
We are using proton 0.12.0 c++ binding API (proton::handler).
We are connecting to a Qpid Java Broker (6.0.0).
We tried to fix the issue by adding a timeout of a big value but it don't s=
eem to affect the behavior.
Unfortunately=2C as this bug is random=2C I don't have a reproducer. It suf=
fises to have a producer and consumer and trying to connect many times unti=
l this error occurs.If you want=2C I can try to have a program which will l=
oop indefinitely with a consumer and a producer connecting until I have the=
 error and I can share that code with you.
This is the code where we set the timeout to 5000 for example:
proton::connection conn =3D e.container().connect(url=2C proton::connection=
_options().idle_timeout(timeout))=3Bconn.open_receiver(url.path())=3B
Regards=2CAdel

> Subject: Re: [Proton-c] Random value of idle timeout causing error when b=
elow 1000
> To: users@qpid.apache.org
> From: gsim@redhat.com
> Date: Wed=2C 25 May 2016 09:55:08 +0100
>=20
> On 25/05/16 09:25=2C Adel Boutros wrote:
> > Hello=2C
> >  From time to time=2C we have this annoying random bug when using proto=
n-c client:
> > Error: amqp:connection:forced: Requested idle timeout of 776 is too low=
. The minimum supported timeout is1000.
> > The value of the timeout is random: sometimes it is as low as "2" and s=
ometimes as high as "998". Re-launching the test makes it pass.
> > Do you know what could be the cause of such error?
>=20
> What api are you using? And what are you connecting to? Is your program=20
> setting the idle timeout itself? Do you have a reproducer you could share=
?
>=20
>=20
> ---------------------------------------------------------------------
> To unsubscribe=2C e-mail: users-unsubscribe@qpid.apache.org
> For additional commands=2C e-mail: users-help@qpid.apache.org
>=20
 		 	   		  =

--_0550c9d7-f636-4418-847f-7c0bc8911630_--