Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@zookeeper.apache.org
Received-SPF: pass (nike.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
From: <Ben.Young@sungard.com>
To: <user@zookeeper.apache.org>
Subject: Is there an easy way to expire a session for testing?
Thread-Topic: Is there an easy way to expire a session for testing?
Thread-Index: Ac8ROexKrS8jgeMqRza0yeY59e9n6w==
Date: Tue, 14 Jan 2014 15:14:47 +0000
Message-ID: 
 <7B36F63619C46A49B86E0D5AB8CDD20061743867@emea-tc2-mb02.internal.sungard.corp>
Accept-Language: en-GB, en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hi=20

Apologies for delibaratly reusing an FAQ item as the title of the question,=
 but it's when I'm trying to implement the suggestion that I'm having issue=
s! I'm currently using the latest C# client, but the code looks identical i=
n the Java client, so it may be applicable to both.=20

I'm trying to reconnect to an existing session using the session id and pas=
sword in order to force an expiry in a unit test. The connection works ok, =
but actually forcing the expiry seems very flaky. The problem seems to occu=
r at the line:

                        SubmitRequest(new RequestHeader { Type =3D (int)OpC=
ode.CloseSession }, null, null, null);

Or=20

            RequestHeader h =3D new RequestHeader();
            h.setType(ZooDefs.OpCode.closeSession);

            submitRequest(h, null, null, null);

in the Java case. In many cases the client is in the state CONNECTION_LOST =
(which seems ok, as it normally reconnects?), so the send fails, but as the=
 client is in the process of shutting down, it's not resent, and so the ser=
ver never gets the explicit expiry, which means the original connection nev=
er gets a SessionExpired error. Is there a unit test anywhere in the codeba=
se that shows how to implement tests like this reliably? I've even tried pe=
rforming the session expiry in a separate process, but this doesn't appear =
to work reliably either

Thanks,
Ben