Dear all,
we are experiencing a big problem with openfire, we went from 300 concurrent users (the connection was really fast) to 8000 concurrent users and each time a client try to connect connection time vary from 5 to 40 seconds even more, in some case minutes.
Our configuration is:
XMPP - Openfire 3.9.3: Windows Server 2012R 64 bit, 8 Core, 32GB
Mysql Server 5.5.6: Windows Server 2012R 64 BIT, 2 Core, 16GB
Please can someone help us since is really a big problem?
If you are using the standard default cache size settings, it is time to fine tune them. I am not an expert on this and cannot advise you of what values to use. However if you look hard enough, you will find valuable posts here that can guide you.
Start with this How many connections can Openfire handle?
Hi Dele,
thanls for your reply. We tried a lot of think, event now we have 3 connection manager deployed. We noticed the server stop to reply, or at least very slow, on this
Connecting
Connected
SENT: <stream:stream xmlns:stream=“http://etherx.jabber.org/streams” id="63445ef
e" xmlns=“jabber:client” to=“messages.whichapp.it” version=“1.0”>
RECV: <?xml version='1.0' encoding='UTF-8'?><stream:stream xmlns:stream="http://
etherx.jabber.org/streams" xmlns=“jabber:client” from=“messages.whichapp.it” id=
“francescoc39072ac” xml:lang=“en” version=“1.0”>stream:features<starttls xmlns
=“urn:ietf:params:xml:ns:xmpp-tls”><mechanisms xmlns="urn:
ietf:params:xml:ns:xmpp-sasl">DIGEST-MD5PLAIN<
/mechanism>CRAM-MD5</stream:features>
SENT:
RECV:
[Version]
V1
[Subject]
CN=John Doe, OU=XMPP, O=Jive Software, L=Portland, S=OR, C=US
Simple Name: John Doe
DNS Name: John Doe
[Issuer]
CN=John Doe, OU=XMPP, O=Jive Software, L=Portland, S=OR, C=US
Simple Name: John Doe
DNS Name: John Doe
[Serial Number]
432E244D
[Not Before]
19/09/2005 04:37:01
[Not After]
29/07/2015 04:37:01
[Thumbprint]
4BEBB26242704B2D1AA6A647F3E5B1E7548C11FD
[Signature Algorithm]
md5RSA(1.2.840.113549.1.1.4)
[Public Key]
Algorithm: RSA
Length: 1024
Key Blob: 30 81 89 02 81 81 00 a3 d4 1d 12 21 f5 bd 4b 4a e9 c2 81 57 99 b3 68
a2 80 87 4d ee f9 56 93 2e 04 d7 e9 a0 f3 68 53 6a 6b f1 d6 0e a7 10 7f ef 8e 7
1 85 e5 2d a4 b6 2a 0b b0 ee 38 b2 85 01 a5 72 13 b2 c7 18 9a 69 69 78 1e 51 03
fc 8f 24 56 ee 60 f0 b0 b2 22 db 75 e2 fc 9f 3f 59 00 fb de 68 6d bd 38 1b 56 30
92 7d a5 8d 1e e3 51 83 12 f8 ce e4 8f de 1c 88 ac 78 1b 57 97 fa 81 87 74 ea 1
6 2d 81 12 aa 77 02 03 01 00 01
Parameters: 05 00
SENT: <stream:stream xmlns:stream=“http://etherx.jabber.org/streams” id="54ca901
8" xmlns=“jabber:client” to=“messages.whichapp.it” version=“1.0”>
RECV: <?xml version='1.0' encoding='UTF-8'?><stream:stream xmlns:stream="http://
etherx.jabber.org/streams" xmlns=“jabber:client” from=“messages.whichapp.it” id=
“francescoc39072ac” xml:lang=“en” version=“1.0”>stream:features<mechanisms xml
ns=“urn:ietf:params:xml:ns:xmpp-sasl”>DIGEST-MD5<mechanis
m>PLAINCRAM-MD5<auth xmlns="http
://jabber.org/features/iq-auth"/><register xmlns="http://jabber.org/features/iq-
register"/></stream:features>
SENT:
[HANGS HERE]
Have you checked your java memory? isn’t it full?
I have tested the simulation environment with 5000 users on a macbook with only 4GB of ram and it wasn’t that bad.
thanks for reply. memory was not the problem, forsome reason openfire literally bombarded the ofpresence table causing the server not able to release db connections. i don’t really now if problem is caused by clients any way i did a work around empting the ofpresence table on a regular basis and everything works well now