|
|
Post by Owl on Mar 10, 2014 8:53:58 GMT -5
Hi,
I've recently been getting disconnected from chat with the message being displayed:
Owl
This user name is already in use.
I'm frustrated that there seems nothing I can do apart from a long wait - often not even 30 minutes wait and refresh helps.
I had sort of thought it was waiting for me to timeout of chat.
Please help, as this birds feathers are flustered.
Owl.
|
|
|
|
Post by CourageouslyLion SeeksSerenity on Mar 10, 2014 9:09:58 GMT -5
|
|
|
|
Post by Greg on Mar 10, 2014 9:22:56 GMT -5
Owl, if you ISP is one that changes your IP you may have been left in the chat in a "ghost" status. This is where your name remains in the chat but you are not really there. So long as it appears in the chat it will not allow you back if your IP is different than the time you initially logged in. If an admin in the chat is aware this has happened they can kick your name out of the chat thus allowing you to log back in. If your IP has not changed you should be able to log back in kicking the "ghost" name out.
|
|
|
|
Post by Owl on Mar 11, 2014 4:37:45 GMT -5
Greg,
Note, I'm still having the problem.
I believe my ISP does change my connection IP address. I occasionally lose connection at either the modem (modem lights off) or at PC level (a guess - as the modem lights are still on).
It seems slightly odd that the IP address is a primary means of identifying the user. I.e. I had hoped the username and password should be significant enough.
I've tried logging out of my SOOS account (thus flushing all connections - i.e. chatroom should disconnect (in a perfect world it should when a logout is received)) and even restarting my browser.
Additionally I use another chatroom using addon chat and it continues to function (it disconnects and has no timeout / ghosting issue) unlike the SOOS room fail. This might imply that some setting/s could resolve the issue.
Why isn't the timeout kicking in?
Owl.
|
|
|
|
Post by Celeste on Mar 11, 2014 15:52:10 GMT -5
Okay, Owl, I've been playing with the settings. Lets see if you still have issues with ghost logins. The reason the timeout doesn't kick in is because it isn't enabled. We can't control the interval and when we've tried it in the past, it would kick chat challengers completely out of the chat room before their 15 minute challenge was over. We got a lot of complaints whenever we tried it, so the other moderators and I decided we can't use it. Edited to add: Your name isn't in the chat list of users online. It makes me wonder if I need to boot everyone out of the chat room at some point to reset it. We'll see. |
|
|
|
Post by Morningstar on Mar 11, 2014 16:16:26 GMT -5
I have found from experience that if I change my screen name in chat and get booted out, I can log back in straightaway - but if my forum user name and chat screen name is the same, I can't until my "chat doppelganger" has disappeared.
HTH
Morningstar
|
|
|
|
Post by Owl on Mar 11, 2014 21:07:44 GMT -5
Celeste,
I had understood there were two different timeout types.
1) Idle timeout - Being no response entered into the chatroom by the user (for a predetermined long period), then the user session is disconnected from the list of users and a disconnect message sent due to being idle.
2) Disconnected session timeout - Being no response received by the chatroom software - where the software periodically (maybe once a minute) sends the chatroom user software a ping message 'are you still connected' (expecting a response), if there is no response (from the user end), then the user is session is disconnected from the list of users due to there being no connection between the chatroom and the user end (a disconnect).
In my response above I assumed the latter when I used the word timeout and expected to be disconnected. It would seem that the № 2 instance must exist in some part - else, I wouldn't have been able to reconnect (in some of those instances that seem to take 30 minutes or more). I.e. № 1 instance would have kept me connected forever as the idle timeout is not enabled - lack of idle timeout can leave a busy chatroom clogged with recalcitrant users who fail to logout their sessions.
---
To test it, I will try to remember and use Morningstar's workaround, with a short username / chatname, I rarely have felt need to change it to something shorter as many users do, e.g. MS
Thanks,
O, the artist formerly known as 'Owl'.
|
|
|
|
Post by Greg on Mar 11, 2014 22:59:45 GMT -5
Owl The timeout setting had nothing to do with your not being able to log back in. The problem was most likely explained in my original reply. That being your IP had changed and your name remained in the chat. That setting has been changed so now even if your name is still in the chat you should be able to log back in even if your IP has changed. 
|
|
|
|
Post by Celeste on Mar 12, 2014 0:32:15 GMT -5
Sorry, Owl. I misunderstood. I do that far too often!  |
|
