What happens with appproxy unregister notification for read_timeout (write_timeout) failed

Hi there,

This is seen from console log running AppProxyProvider. Sometimes can see like this:

nw_endpoint_handler_set_adaptive_write_handler [C978 IPv4#759261e2:443 ready socket-flow (satisfied (Path is satisfied), viable, interface: en0, ipv4, dns)] unregister notification for write_timeout failed

Would like to see with you guys what is going on when such logs on show? Is it because the peer flow (connection or session) closed and the local connection (session) timeout?

As it have seen with that appproxy gets blocked for a while and then recovers. Is it normal and is it avoidable?

Thanks in advance for any suggestion.

Would like to see with you guys what is going on when such logs on show? Is it because the peer flow (connection or session) closed and the local connection (session) timeout? As it have seen with that appproxy gets blocked for a while and then recovers. Is it normal and is it avoidable?

If the peer flow closed the connection I am assuming that an error or failure would immediately be noticeable. What I "think" is going on here is the data was written to the connection (looks like the remote side) and the connection just timed out because the actual remote endpoint was lost or timed out for some reason.

Matt Eaton
DTS Engineering, CoreOS
meaton3@apple.com
What happens with appproxy unregister notification for read_timeout (write_timeout) failed
 
 
Q