Mailing-List: contact esme-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: esme-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of vdichev@gmail.com designates
 209.85.220.224 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type
         :content-transfer-encoding;
        b=TSl8F3ooPSdZK8+zkINtpsyz22v75OqmYEzKLt/BWpgdP9GYtnN3EcjeIuYLlh4wrW
         wCDGcledmFsfW6KmxhuCYnmf2bxtZJEZZvNGevmJpfRQinXZl7XOiRBeuWkdZGSGAlxS
         SUXT5C6emQEe9JX/o66x4NHDzhzyM3csD6h5k=
MIME-Version: 1.0
Sender: vdichev@gmail.com
In-Reply-To: <cdbebedf0908310850w64a89a08o68a88cc44b17ecd2@mail.gmail.com>
References: <c7fc82820907190320t35c30adbqa46649522ceee210@mail.gmail.com>
	 <cdbebedf0907270617x1bee775dtbc0acf5043536fd5@mail.gmail.com>
	 <c7fc82820907271329m34217186o61a6b64560636889@mail.gmail.com>
	 <cdbebedf0907292015x4f014740u983fce10218654c8@mail.gmail.com>
	 <c7fc82820907310017u6e69d617o4dd2afcc2a786d42@mail.gmail.com>
	 <cdbebedf0907310657i4ab257fcn3a641c3db29573ed@mail.gmail.com>
	 <c7fc82820908161616t6c74d025ha6fdb672c440ade6@mail.gmail.com>
	 <cdbebedf0908271038h131e2bffpec9658601ee239d8@mail.gmail.com>
	 <c7fc82820908302150p39a4b0dfs2f291184133b71d@mail.gmail.com>
	 <cdbebedf0908310850w64a89a08o68a88cc44b17ecd2@mail.gmail.com>
Date: Tue, 1 Sep 2009 07:51:38 +0300
Message-ID: <c7fc82820908312151o3efdc7dav297bbb6492fa529d@mail.gmail.com>
Subject: Re: [Lift] JSON handler doesn't respond
From: Vassil Dichev <vdichev@apache.org>
To: esme-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I built Lift locally and put dumps in LiftSession's cleanupUnseenFuncs
and updateFuncByOwner. So far I cannot reproduce the problem.

>> =A0 =A0<snapshot>
>> =A0 =A0 =A0<buildNumber>1724</buildNumber>
>> =A0 =A0</snapshot>
>> =A0 =A0<lastUpdated>20090828152733</lastUpdated>
>>
>> Do I have the correct updated jar?
>>
>
> I have no idea.

Since you've mentioned in the past that you're using hudson for
building the lift jars before they're uploaded to the public maven
repo, I was hoping that one can associate the build number or date
with the specific commit.

> Can you specify the exact steps to reproduce the problem? =A0I have reall=
y,
> really tried to make it happen and can't. :-(

I'm using Firefox, on different versions of Linux. I have three users
(e.g. a follows b, b follows c) and I open up the ESME main page in a
separate browser for each user. I post a message for each to make sure
it works. I leave the browsers open and after a while I check again
whether I can send a message with all users. Usually half an hour is
enough for 2-3 of the users to block. The problem can always be
reproduced on the Stax instance, too, by just leaving a session open-
Dick can confirm that it regularly happens to him, too. Maybe he can
add some details on how he reproduces it.

Let's see if the fix works this time. If not, the only difference I
can think of is the browser- you could be using Chrome or Safari. I've
tried reproducing with Chrome in the past once or twice and couldn't.

Vassil