[SR-Users] websocket sometimes log errors after ws connect has closed

[Vasiliy Ganchev]

additionally:
version: kamailio 4.2.5 (i386/linux)
flags: STATS: Off, EXTRA_DEBUG, USE_TCP, USE_TLS, TLS_HOOKS, USE_RAW_SOCKS,
DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC,
F_MALLOC, DBG_F_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE,
USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.

I looked in sources of websocket module from latest master, there is not
huge changes, and as seems to me nothing that can change behaviour of my
issue.
 
Websocket configuration part from configs:

# websocket
modparam("websocket", "keepalive_timeout", 30)




--
View this message in context: http://sip-router.1086192.n5.nabble.com/websocket-sometimes-log-errors-after-ws-connect-has-closed-tp144092p144093.html
Sent from the Users mailing list archive at Nabble.com.