: Monday, July 21, 2014 11:56 AM
To: 'dev@httpd.apache.org'
Subject: RE: Question about async mod_proxy_wstunnel and threads
My client and server are based on sample code included with the ws4py
package (http://ws4py.readthedocs.org/en/latest/). We use CherryPy and
the ws4py package contains
@httpd.apache.org'
Subject: RE: Question about async mod_proxy_wstunnel and threads
My client and server are based on sample code included with the ws4py
package
(http://ws4py.readthedocs.org/en/latest/). We use CherryPy and the
ws4py package contains a CherryPy-based
: Question about async mod_proxy_wstunnel and threads
I think I've found the issue; there's an extraneous apr_pollset_remove() call
in event.c:1978. Relevant code (double-slash comments are mine):
/* We only signal once per N sockets with this baton */
if (!(baton-signaled)) {
baton
On Fri, Jul 25, 2014 at 12:01 PM, Steve Zweep
steve.zw...@watchguard.com wrote:
ProxyWebsocketAsyncDelay
Currently the default is seconds. If you want millseconds, you have to
add the ms suffix. Maybe the doc needs a tweak, but I think whole
seconds by default is best.
--
Eric Covener
unfinished ...
- Steve
-Original Message-
From: Steve Zweep
Sent: Monday, July 21, 2014 11:56 AM
To: 'dev@httpd.apache.org mailto:dev@httpd.apache.org'
Subject: RE: Question about async mod_proxy_wstunnel and threads
My
-
From: Steve Zweep
Sent: Monday, July 21, 2014 11:56 AM
To: 'dev@httpd.apache.org mailto:dev@httpd.apache.org'
Subject: RE: Question about async mod_proxy_wstunnel and threads
My client and server are based on sample code included with the
ws4py
I removed the apr_pollset_remove() call on line 1978 of event.c. So far it is
working fine for me. Thanks Edward.
- Steve
Edward Lu wrote:
Seems like the solution is just to remove the extra apr_pollset_remove(); all
sockets are removed from the pollset when
one of them is signalled. If
@httpd.apache.org'
Subject: RE: Question about async mod_proxy_wstunnel and threads
My client and server are based on sample code included with the ws4py package
(http://ws4py.readthedocs.org/en/latest/). We use CherryPy and the ws4py
package contains a CherryPy-based server (attached).
The client
21, 2014 11:56 AM
To: 'dev@httpd.apache.org'
Subject: RE: Question about async mod_proxy_wstunnel and threads
My client and server are based on sample code included with the ws4py
package (http://ws4py.readthedocs.org/en/latest/). We use CherryPy and
the ws4py package contains a CherryPy
Subject: Re: Question about async mod_proxy_wstunnel and threads
I guess it is kind of telling that we could still respond to the write from
client 2, there are probably more potential errors that make us lose track of
both sides simultaneously.
Can you share your ws client and server if they're easy
Monday
though.
- Steve
-Original Message-
From: Yann Ylavic [mailto:ylavic@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
. The same results were observed.
- Steve
-Original Message-
From: Eric Covener [cove...@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
results were observed.
- Steve
-Original Message-
From: Eric Covener [cove...@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
to this before Monday though.
- Steve
-Original Message-
From: Yann Ylavic [mailto:ylavic@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
, 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 this
fix: http://svn.apache.org/r1605769.
I don't think there is a released version with this patch...
Regards,
Yann
Hi
I am prototyping a system in which we will have a large number of websocket
connections between multiple clients and a server (potentially) behind
mod_proxy_wstunnel. Currently I am testing a trunk build with the event mpm.
With ProxyWebsocketAsync turned off, communication between client
On Thu, Jul 17, 2014 at 2:09 PM, Steve Zweep steve.zw...@watchguard.com wrote:
1. While communication from client to server works well, unsolicited
messages from the server to clients seem to queue. If the client
subsequently sends a message back to the server, the original message from
-Original Message-
From: Eric Covener [mailto:cove...@gmail.com]
Sent: Thursday, July 17, 2014 2:27 PM
To: Apache HTTP Server Development List
Subject: Re: Question about async mod_proxy_wstunnel and threads
On Thu, Jul 17, 2014 at 2:09 PM, Steve Zweep steve.zw...@watchguard.com wrote:
1
packets are sent by the server.
- Steve
-Original Message-
From: Eric Covener [mailto:cove...@gmail.com]
Sent: Thursday, July 17, 2014 2:27 PM
To: Apache HTTP Server Development List
Subject: Re: Question about async mod_proxy_wstunnel and threads
On Thu, Jul 17, 2014 at 2:09 PM
. A tcpdump shows the
correct packets are sent by the server.
- Steve
-Original Message-
From: Eric Covener [mailto:cove...@gmail.com]
Sent: Thursday, July 17, 2014 2:27 PM
To: Apache HTTP Server Development List
Subject: Re: Question about async mod_proxy_wstunnel
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
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
22 matches
Mail list logo
