Comments on: jwchat.org updated to fix problems with FF3

By: Steve

Steve — Tue, 16 Dec 2008 18:27:08 +0000

Well sorry, I don’t know what might be wrong, but it’s all working just fine here.

By: Stan Brower

Stan Brower — Tue, 16 Dec 2008 17:53:06 +0000

I’m using FF3, but its still not working , The message still isn’t showing up at the other side.

By: Steve

Steve — Thu, 18 Sep 2008 06:11:26 +0000

Which version of JSJaC are you using? You need to use the latest from SVN. I’ll release a new tarball within the next days to fix these issues.

By: satheesh

satheesh — Thu, 18 Sep 2008 05:08:43 +0000

Hi,

i am using jsjac.it is working fine with IE and FF2.but not working in FF3.anybody have the sollution ?

By: pablo

pablo — Sun, 31 Aug 2008 00:13:00 +0000

Steve,

I’ve made a test and sent packets with id in the wrong order and got the same error in the log as in my previous post so I’m sure this is the cause.

I understand that JSJAC can’t make sure requests arrive at the correct order to the server and the server should wait for the older request.
Are you saying that this is should be already implemented in ejabberd?

Do I need to define the ‘hold’ attribute or something else when I connect to ejabberd using a client?

Do you have any idea what can cause the exception from my previous post and how to fix it?

By: Steve

Steve — Wed, 27 Aug 2008 08:51:26 +0000

Pablo, what you see here unfortunately is an exception within in ejabberd’s http-bind module not a correct termination of the session.
According to the specs of the BOSH protocol a session is to be terminated if a request id is not within a certain ‘window’ regarding the last successful/known request (should be +/- 2).

JSJaC takes care automatically to not mix requests but as with http you can’t tell for sure when/if a request arrives at the server, thus if two concurrent requests allowed there might be a situation where the one with the higher request id could be seen first by the server. it’s got to wait then for the older request to arrive and bring them into correct order.

By: pablo

pablo — Sat, 16 Aug 2008 22:24:45 +0000

I’ve noticed that in your ejabberd http-bind module you don’t allow the client to mix messages.
If a client sends two messages with rid and rid+1 and the order is mixed in the way to the server you end the session.

The error report:
=ERROR REPORT==== 2008-08-03 16:59:55 ===
** State machine terminating
** Last message in was {’$gen_sync_all_state_event’,
{,#Ref},
{http_put,838862407,
[{"xmlns",
"http://jabber.org/protocol/httpbind"},
{"rid","838862407"},
{"sid",
"56bf251ff0aa097abc4647cf72407444e55787bb"}],
[],1,[]}}
** When State == loop
** Data == {state,”56bf251ff0aa097abc4647cf72407444e55787bb”,838862408,
[],[],[],
{,ok},
,0,
{,#Ref},
#Ref,1217797195572325,undefined,0,
[{hbr,838862408,[],[],[]}]}
** Reason for termination =
** {{badmatch,[]},
[{ejabberd_http_bind,handle_sync_event,4},
{gen_fsm,handle_msg,7},
{proc_lib,init_p,5}]}

Does my diagnose sound reasonable to you?

I wonder if in jsjac you use some kind of timeout to ensure that this situation won’t happen.

By: Wielkiebe

Wielkiebe — Tue, 22 Jul 2008 09:34:33 +0000

For me, still don’t work with ff3 :/

By: Vadim Berezniker

Vadim Berezniker — Fri, 11 Jul 2008 07:24:45 +0000

I installed CVS version of jwchat today, but sent messages are still not showing up at the recipient.

By: Jason

Jason — Thu, 03 Jul 2008 08:55:35 +0000

in the jwchat.org create two account, one account login in JWchat in a Firefox3 other login in Psi (the Jabber client), Psi can send message to JWChat but JWChat can not send to PSI

this is really big big bug, any solution please help me, thank you very much