#1800 mod_websocket: cleanly-closed sessions are hibernated by mod_smacks
Reporter
MattJ
Owner
Nobody
Created
Updated
Stars
★ (1)
Tags
Status-Fixed
Type-Defect
Priority-Medium
MattJ
on
What steps will reproduce the problem?
1. Enable mod_websocket and mod_smacks
2. Connect and log in using a websocket connection
3. Cleanly close the session
What is the expected output?
A cleanly-closed session should not hibernate.
What do you see instead?
mod_smacks tries to hibernate the session (typically leading to a "hibernating too long" timeout a little later).
What version of the product are you using? On what operating system?
Reproduced in Prosody 0.12.2
What steps will reproduce the problem? 1. Enable mod_websocket and mod_smacks 2. Connect and log in using a websocket connection 3. Cleanly close the session What is the expected output? A cleanly-closed session should not hibernate. What do you see instead? mod_smacks tries to hibernate the session (typically leading to a "hibernating too long" timeout a little later). What version of the product are you using? On what operating system? Reproduced in Prosody 0.12.2
Fixed in https://hg.prosody.im/trunk/rev/0598d822614f and confirmed.
Changes