Hi,
I recently installed ver15.02 with our custom client using asmack library. ejabberd is installed on Ubuntu ver14 with Apache, MySQL and PHP (bitnami stack). The Client uses BOSH connection to the server.
The client can register, login and send presence packets fine and everything is quite fast initially. After login we show our android UI and also send the presence packet. Once this process is over the client(asmack) library sends the ping messages to the server. It seems that it takes 60seconds for the reply to come back. Until the reply comes back the next packets are blocked and don't get processed. So if we need to get info via IQ the client waits for 60 seconds.
This is also not scalable when we send messages between clients. The 2 clients can see each other's online presence and sends event notifications (like composing, paused, online) before sending the message but each message takes 60 seconds to complete so at the end the message gets delivered after several minutes.
Many times the server times out the client and closes the connection. The timeout value we see is 30 seconds (inactivity) and there is another timeout value of 60seconds seen in the xml packets that server sends to the client.
I would really appreciate if someone could please help us configure it right.
Thanks,
Nitin
Did you try with a standard
Did you try with a standard XMPP client instead of a custom one ?
There is a chance the problem is a lock in the client before investigating configuration issues in ejabberd.
Could you please suggest an
Could you please suggest an xmpp client?
Also what are the things client might be doing wrong? eg, we create a separate thread to send the packet instead of doing it in the UI thread. Another thread receives the packet and notifies the client.
Thanks,
Nitin
You can try your server using
You can try your server using Psi or Gajim. If you do have those latency there, then the problem is in your custom implementation.