Widget stuck to send messages

[eodin]

I've tested NodeJS connection durability and found the issue. Once NodeJS process died on server widget can't push messages anymore until operator's message will be received. Even after nodejs restart it still work one-way.

visitor: hello
operator: hello. can I help you?

[socket.io.js terminated]

visitor: I have major issue
visitor: when I'm trying to login my account I see other's name and balance
visitor: I even able to withdraw his money

[socket.io.js restored]

visitor: Any comment?
visitor: operator are you there?
operator: what's the problem? (just getting prev messages)
visitor: WTF

[remdex]

Sorry, but it's not enough steps to reproduce... Why does NodeJS died?
If i correctlu understood your test workflow was:

1. Shutdown nodejs
2. Wait untill connection is closed.
3. Turn on NodeJS, after that even if users connects they cannot chat

Is that the case you are trying to describe?

[eodin]

Almost. I've tested that happens with alive session during nodejs restart for example

1. open chat http://chat/
2. accept operator chat at http://chat/site_admin/
3. shutdown nodejs
4. test chat still work but only one-way now
5. run nodejs again
   5 . make sure what widget switched back to nodejs but still works if only operator send a message

[remdex]

That's more detailed report:) I'l see what i can do about that :)

[remdex]

Implemented.