tsung icon indicating copy to clipboard operation
tsung copied to clipboard

tsung receiving blank responses for xmpp

Open simar27 opened this issue 8 years ago • 3 comments

i am running tsung with wss connections to the server and have set ack=local , so, my next request should be sent out only when i have received the earlier request's response. But instead, due to these empty receive resonses as shown in tcpdump file, the tsung is sending out the next request without even handling the earlier response . how are these empty responses from the server handled by tsung and could it be ping messages from the server which are accounting for these blank messages.

simar27 avatar Oct 05 '17 06:10 simar27

Which version are you using ? version 1.7.0 should handle IQ ping messages, maybe it can solve your problem

nniclausse avatar Oct 12 '17 21:10 nniclausse

i am using version 1.6.0 and i was handling the pings from the server by sending pongs in ts_server_websocket.erl file by creating a check. Now, this ping coming from the server is going to the upper layer (ts_client.erl) and getting handled as the response to the earlier request sent by the tsung when ack= local and then sending the next request from tsung without even handling the earlier request. ideally, it should have not considered this as the response and waited for the actual response.

simar27 avatar Oct 13 '17 07:10 simar27

@simar27 have you tested this against tsung 1.7.0? Also, is this maybe related to https://github.com/processone/tsung/pull/289?

tisba avatar May 30 '18 11:05 tisba