Logoff sometimes doesn't work (2.0 client, 2.1 server)

All Union Platform questions, comments, feature requests, and bug reports.

Logoff sometimes doesn't work (2.0 client, 2.1 server)

Postby toby » Tue 02 Dec 2014 20:29

Again, using Orbiter 2.0 with UnionServer 2.1
(I'm beginning to think maybe the compatibility isn't quite there)
on *some* occasions I get this error in the client console log:

"12/2/14 16:21:53.708 UTC-8 WARN: [ACCOUNT_MANAGER] Logoff failed. The current user is not logged in."

However, looking at UnionAdmin, the contrary is definitely the case.
The logoff UPC never getting sent to the server means that as far as the server
is concerned this client definitely IS (still) logged in.

Unfortunately, that's all the information I have - and *sometimes* it does in fact work ok.
toby
 
Posts: 162
Joined: Sun 24 Jun 2012 14:18

Return to Union Platform

Online

Users browsing this forum: No registered users and 9 guests