I am trying to use Jitsi Hammer to stress-test a server with a large number
of users simultaneously streaming.
If I join the TestHammer room with another client, I can see 5 hammer users
log in however they do not stream data. (I simply see the default robot
avatars the default meet client provides)
I am running hammer with the following arguments:
-BOSHuri https://meet.mysite.com/http-bind/ -users 5 -ivf
-room TestHammer -allstats -overallstats -summarystats -length 10
I have added the remote servers cert to my local java keystore (preventing
initial ssl errors).
running stat on the bib-buck-bunny file, I see that the program is not
accessing it. I believe there is a communication problem between the client
and server before the file is ready to be streamed.
Tracing through the Hammer java application at runtime, I see much of the
logic in FakeUser.java working. There is a call to start(), followed by
connectMUC(), and the server sees the Hammer users log in.
However I never see a callback to FakeUser.processPacket(). It's as if the
client can reach the server, but the server responses are lost in transit.
I have other client applications that work with this server. Namely the
default client featured at meet.jit.si, as well as another I've built using
lib-jitsi-meet. I have tried running hammer on 3 different systems with
different network configurations, all extremely permissive and capable of
running other jitsi clients. This does not appear to be a firewall issue.
Does anyone have insight as to what could be preventing my hammer client
from receiving communications from the server?