WebSocket / BOSH ping problem
I have a strange problem, in the way I get pings to the different clients.
I have several client which have different transports - some are running BOSH, some WS (WebSockets) and some normal TCP.
My properties for ping is like so:
So for TCP I receive the ping and can answer back with a pong - but for WS I do not receive such a IQ stanza. So it gets terminated after my watchdog timeout.
The same for BOSH, but I believe that BOSH does not need such a ping feature since its request/response model.
My WS is setup like so:
@--comp-class-1 = tigase.server.websocket.WebSocketClientConnectionManager
--comp-name-1 = ws2s
I can se that I am present with all my clients.. so they should receive a ping like the TCP one.
Stream management is enabled (XEP-0198) and I am running Tigase server 7.0.2-b3821/563fcf81 (in single node mode - no cluster and directly on the server).
Added by Wojciech Kapcia about 3 years ago
If you prefix property with "c2s/" it applies only to regular socket connections. You can either configure watchdog separately for @ws2s/@. Also - watchdog is disabled for BOSH as it doesn't make sense to check those connections using watchdog - appropriate checking is inherent in BOSH itself.
Added by Steffen Larsen about 3 years ago
I've set it like this, and my TCP client gets XMPP ping, but my WS client gets whitespaces.. hmmmm