Can't send message on the wall after some timeout on xmpp

Bug #1105567 reported by Adrien Dorsaz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Movim
Won't Fix
High
edhelas

Bug Description

It seems that Bosh on Prosody (0.9 from trunk) has a timeout for session, but Movim doesn't respect this timeout.

For example, if I log on Movim at morning, then I leave my PC suspended and come back in the afternoon, so Movim is still connected (I can use the opened page).
Then I try to create new message with this Movim connection, so Movim remove my message from the editor and is unable to get it back on the wall because bosh session was closed by Prosody server before.

Fix will be to automatically disconnect if BOSH server doesn't respond or prompt user to get again password and try to send again message.

Bosh error in my logs :

Jan 26 00:52:23 mod_bosh info Client tried to use sid '5e5e0dea-2f22-439f-ab8e-6020bb3462ec' which we don't know about

edhelas (edhelas)
Changed in movim:
importance: Undecided → High
milestone: none → 0.7
assignee: nobody → edhelas (edhelas)
Revision history for this message
edhelas (edhelas) wrote :

I close this bug, since Movim 0.9 we're using WebSockets

Changed in movim:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.