Project

General

Profile

Connection closed after few seconds while testing with Tsung

Keren Meir
Added about 5 years ago

Hi,

I'm testing the XMPP tigase server with Tsung.

My test configuration: 12.5 connection per second, each connection stay connects for ~2000 second.

In one test I read user and password from csv file (username;password) while in the other test the username and password where in the xml tsung file.

The second test works perfect, but the first one isn't.

I saw in wireshark (the test with the csv file) that each connection was closed after 6 second.

I check in the Tigase log and saw many line: "Found trying to find stale XMPPResourceConnection by userId ..."

Why is this happened? What does this log means...?

Thanks


Replies (3)

Avatar?id=6023&size=32x32

Added by Artur Hefczyc TigaseTeam about 5 years ago

First of all what Tigase server version are you trying to test. There is nothing wrong in general, with the log entry you found, however, some earlier version did not handle that part efficiently enough. This has been corrected in recent version. It does not affect the test, except that excessive logging may slow down the server and affect performance. This log entry just means a user has disconnected and the server is cleaning internal data collections.

The 6 seconds connection close probably means authentication was not successful.

As for the Tsung. We are not Tsung authors and we are not experts at Tsung so the help we can offer is really limited. I have never been able to make Tsung work with accounts in cvs file. I could only make it work with automatically generated usernames and passwords: user1, pass1, user2, pass2, ......

Added by Keren Meir about 5 years ago

  1. The Version of the Tigase is 5.2.0 beta3.

  2. In the trace (wireshark) I saw that the authentication succeed and the client ask "get roster" and than the connection closed.

  3. Did you tried to load users from csv file and it didn't work as well? Or you just use the automatically generating?

Thanks

Avatar?id=6023&size=32x32

Added by Artur Hefczyc TigaseTeam about 5 years ago

Keren Meir wrote:

  1. The Version of the Tigase is 5.2.0 beta3.

  2. In the trace (wireshark) I saw that the authentication succeed and the client ask "get roster" and than the connection closed.

I do not have explanation for this. The best way to track this down would be lowering traffic from Tsung to minimum, turning heavy logging on in Tigase and check if there is any hint on the Tigase side. Tsung does generate some logs and errors but I do not understand them.

  1. Did you tried to load users from csv file and it didn't work as well? Or you just use the automatically generating?

We were able to get Tsung working only with user/password automatically generated.

    (1-3/3)