does the ejabberd 2.1.0 use ER12?
and the "send_timeout" will be fixed in the release?
Looking for ejabberd docs?
To access the most up-to-date ejabberd documentation, please visit docs.ejabberd.im »
when does the ejabberd 2.1.0 released?
Submitted by xmukmb on Tue, 2009-04-28 02:54
when bugs are fixed
when does the ejabberd 2.1.0 released?
The releases don't have a fixed or planned date. ejabberd 2.1.0-beta1 will be released when it doesn't have open tickets (bug reports).
does the ejabberd 2.1.0 use ER12?
Do you mean if it will work correctly with Erlang/OTP R12B-5?
ejabberd 2.1.0 will work with R11, R12, and probably also with R13. The best Erlang version for ejabberd 2.1.0 will be R12B-5.
and the "send_timeout" will be fixed in the release?
What error is that: do you have the link of the ticket?
the link
and the "send_timeout" will be fixed in the release?
What error is that: do you have the link of the ticket?
this is the link:
i saw it in the mailing list,Mickaël Rémond said that it will be released in 2.1.0, and i want to make sure that.:)
You can try the changes.
It seems now the patch in EJAB-217 is not planned for ejabberd 2.1.0. But you can try it anyway:
I've downloaded source code of ejabberd 2.0.5, applied the patch, and compiled it with Erlang R12B-5. I've uploaded a zip with the patch, source code and changed files here: .
If you run ejabberd 2.0.5 and Erlang R12B-5 (it is included in the ejabberd binary installers), then you can try this by simply overwriting the beam files in your installation with the beam files included in the zip.
ok,i will try it,thank you
ok,i will try it,thank you very much!
i am sorry to say that the
i am sorry to say that the change just improve a little in perforrmance, but not enough for my situation。
without the change, a node just can work with about 900users in a room, and about 10 messages per second in this room.
and now it can work with about 900users in a room, and about 20 messages per second in this room.
if i send more messages, the memory still glow up quickly and finally crashed out of memory.
i can use more nodes to work for this, the performance can be lower, the message that can not be processed can be throw out, but the server can not crash out.
does ejabberd have something to do with this?
what can i do for it ?
plz help me!!