Hello,
we are currently doing performance tests to check the number of users that could be simultaneously connected on a wildfire server.
Of course we plan to use connection managers but in a first phase we would like to be able to see what the server as standalone can do and to well understand its capabilities, limitations in order to tune it.
To generate an important traffic, we use tsung to play several scenarios to generate much traffic of different kinds (presence, messages especially). But as soon as we reach around 10000 users (with a 4 processors machine with 4 GB dedicated to the VM if I am right), we face some weird behavior.
It is like users become disconnected. Suddenly we lose several users and reach 7000 connections and we see the following error messages:
2006.08.22 18:36:11 Closing session due to bad_namespace_prefix in stream header. Prefix: null. Connection: org.jivesoftware.wildfire.net.SocketConnection@731f3f socket: Socket[addr=/10.0.0.39,port=38806,localport=5222] session: null
and
+2006.08.22 18:36:11 org.jivesoftware.wildfire.net.BlockingReadingMode.run(BlockingReadingMode.java:1 04) Connection closed before session established
Socket[addr=/10.0.0.39,port=38806,localport=5222]+
We are not able to understand until now if the problem comes from tsung or if it is an implementation inside wildfire server to reject too many sessions in case of memory problems (anyway we did not observe any memory problem during the test) or something else.
Maybe someone could be of some help …
Maybe someone did similar tests even with other tools and had same or different results.
Any idea, any help is welcome.
Thanks in advance for your help.
Best Regards
Pascal