1

I was recently working on a web application that uses Strophe.js (http://strophe.im/strophejs/) behind Candy (http://candy-chat.github.com/candy/). The client gets a 404 from ejabberd due to invalid rid issue when it sends messages too fast. The same error occurs at random times as well.

After some research I figured out that this is due to invalid rid issue and it is happening because ideally client-side js should wait for server response before pushing a new stanza while it does not in some cases.

From my point of view this should be ensured by Strophe.js at low level rather than the application programmer. Please tell me how should I proceed to fix this problem? I could not find solution to this problem on Google.

Mickaël Rémond
  • 9,035
  • 1
  • 24
  • 44
Saurabh Kumar
  • 195
  • 3
  • 12
  • You might ask at the strophe.js mailinglist. Usually this shouldn't happen. I don't know why this happens and without any sourcecode or logs it's quite hard to tell what's going wrong. – Michael Weibel Dec 07 '12 at 08:59

1 Answers1

0

Must be an issue with Ejabberd version. Was an know issue fixed now in 2.1.12 https://www.process-one.net/en/ejabberd/release_notes/release_note_ejabberd_2.1.12/

The issue was that ejabberd was receiving messages ids (RID) in the wrong order, then closed the connection with an 404. Now this behavior has been removed (and only happends if receives the SAME RID, to avoid replays)

Hope this helps!

Javier D. Caruso

JavierCaruso
  • 305
  • 1
  • 4
  • 13