Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (nike.apache.org: domain of ylavic.dev@gmail.com designates
 209.85.213.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <56C2E06F97EACF4FB2F1B31EEFC4493091FA9C6B@mbx2.wgti.net>
References: <56C2E06F97EACF4FB2F1B31EEFC4493091FA8B62@mbx2.wgti.net>
	<CALK=YjPh75EuCBm6vMbAO0kzJWH0EEoteuCx3rJW+toQ_POP=w@mail.gmail.com>
	<56C2E06F97EACF4FB2F1B31EEFC4493091FA9160@mbx2.wgti.net>
	<56C2E06F97EACF4FB2F1B31EEFC4493091FA9A51@mbx2.wgti.net>
	<CAKQ1sVMe8G39C11zfZv1FFcVXUFBrO13yE5JXj_wrfcAnG6cRQ@mail.gmail.com>
	<56C2E06F97EACF4FB2F1B31EEFC4493091FA9C6B@mbx2.wgti.net>
Date: Fri, 18 Jul 2014 23:50:09 +0200
Message-ID: 
 <CAKQ1sVPqsoFsRHd+OEJV5b2untghWG_8TVjR9pUFo62k+U6K7A@mail.gmail.com>
Subject: Re: Question about async mod_proxy_wstunnel and threads
From: Yann Ylavic <ylavic.dev@gmail.com>
To: httpd <dev@httpd.apache.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Probably a false trail, trunk at r1611741 is up to date, I think 1.5.x
won't help.

On Fri, Jul 18, 2014 at 11:35 PM, Steve Zweep
<Steve.Zweep@watchguard.com> wrote:
> Hi Yann,
>
> The test I ran today was built with APR from trunk (r1611741). I see that=
 r1605769 modifies apr_skiplist.c and there has been a lot of activity in t=
he  trunk version of that code lately. I can try with the 1.5.x branch code=
 to see if it makes a difference. Probably won't get to this before Monday =
though.
>
> - Steve
>
> -----Original Message-----
> From: Yann Ylavic [mailto:ylavic.dev@gmail.com]
> Sent: Friday, July 18, 2014 4:51 PM
> To: httpd
> Subject: Re: Question about async mod_proxy_wstunnel and threads
>
> Hi Steve,
>
> can you still reproduce with the latest APR 1.5.x, notably containing thi=
s fix: http://svn.apache.org/r1605769.
> I don't think there is a released version with this patch...
>
> Regards,
> Yann.
>
> On Fri, Jul 18, 2014 at 9:38 PM, Steve Zweep <Steve.Zweep@watchguard.com>=
 wrote:
>> I've attached annotated logs that show the issues I described. Both scen=
arios have ProxyWebsocketAsync turned on. The first does not use the AsyncD=
elay and shows how server messages stall and are not delivered until the cl=
ient polls. The second has ProxyWebsocketAsyncDelay set to 100. In that cas=
e, message processing works properly, but threads are held open and there i=
s no sign of async processing.
>>
>> Since my build and execution environment were somewhat non-standard, I r=
epeated all the tests today on stock Ubuntu 14.04, with a fresh checkout an=
d build of httpd and apr trunk code. The same results were observed.
>>
>> - Steve
>>
>>
>>
>> -----Original Message-----
>> ________________________________________
>> From: Eric Covener [covener@gmail.com]
>> Sent: July 17, 2014 9:15 PM
>> To: Apache HTTP Server Development List
>> Subject: Re: Question about async mod_proxy_wstunnel and threads
>>
>> I am having trouble seeing it mis-behave. w/ Async and AsyncDelay, I
>> am seeing the expected trace messages and when I look at backtraces of
>> httpd I can see zero threads in wstunnel . If I send a server msg, I
>> get it ASAP in the client -- and then I see 1 thread in poll for the
>> right couple of seconds
>>
>> Can you grab trace at e.g.
>>
>> LogLevel INFO proxy_wstunnel_module:trace8
>>
>> And annotate the timing a bit for what you do in the client?  Is it poss=
ible you have an un-updated trunk from several weeks ago?  There was an opt=
imization put in and backed out that might have broke some of these same th=
ings for a very short window.
>>