4:11:51,289 INFO [pool-1-thread-1] sessions.DefaultSessionManager - Session removed: { Id: 8432, Type: DEFAULT, Logged: Yes, IP: yyyy:56527 }
14:11:51,289 INFO [SocketReader] sessions.DefaultSessionManager - Session removed: { Id: 8432, Type: DEFAULT, Logged: Yes, IP: yyyy:56527 }

These are the ...

Hi,
we are using the force login setting within our zone. Most of the times a user is disconnected by this feature, we recieve an error like this one:


14:11:51,289 INFO [pool-1-thread-1] entities.SFSZone - User already logged in. Disconnecting previous instance : ( User Name: xxxxx, Id: 8001 ...

Because we are storing various other client settings within the same xml file.

Hi,

I am trying to set the BlueBox settings in sfsclient.config (ConfigData) which does not work, because I am not loading the server settings via loadConfig. (I use my own config loader). Is there a way to force the sfsclient to create ConfigData?

Dirk

Ok, we will do so.

Thanks.

Thanks for your answer. Intreresting topics. But I ment, that we have exactly the same problem: not running any phyton extensions and massive garbadge collection of phyton classes.

We know deleted the webapps like you suggested. But I was wondering if that helped in the above case.

Dirk

Was there a solution for this problem? Because we are experiencing the same thing right now.

Thanks.

Dirk

Hi, thanks for your explenation.
Yes, this seems like a misunderstanding. I assumed, that a limbo room does not receive ANY uCount updates. None from its own room, nor of any others.
We never had any problems with the ucount in the other room, because we request a new roomlist when ever a user ...

Sure,

<Rooms>
<Room name="AA" maxUsers="5000"/>
<Room name="BB" limbo="true" maxUsers="10000"/>
</Rooms>

We use this room setup to first send all users to room AA where they can interact with each other (chat, view user lists...). In special situations we send them to room BB where they are just ...

When the limbo flag is turned on, the room suppresses certain events (new user arrived, user left, user count changed, room and user variables) and inhibits the ability to send public messages.

It looks like that setting the room to limbo is not enough to prevent the broadcasting of uCount ...

Hi,

lets ignor any lagging problems.

What could cause the roundTrip error? It is flooding the logs and I hav no idea where it comes from.

Is there any specific info I could give you that might help at least to point in a direction where to look further ?

Thanks.

Dirk

This could be an issue.
We needed the forceLogout option prior to version 1.6.3. Thats what we did to achiev this:
// log out already logged in user
SocketChannel existingUser = zone.getChannelFromName(nick);
if (existingUser != null) helper.disconnectUser(helper.getUserByChannel(existingUser ...

Hi,

we have changed the code but still have problems with users we can not disconnect. The only way to remove them is by restarting the server.

...any idea? any more infos I can give you?

Dirk

...no more ideas?

Version 1.6.3

The admin panel indicates that there is no problem with neither of the message handlers. All og them show 0 messeges waiting and the load is arround 0 %. The most dropped messages we had were 203 - but not right when this happended.

Dirk