Hi,

Have you done some benchmarks on the 2X?
I am interested in how many users can one SFS 2X server can hold in limbo rooms. We expect ~ 200K concurrent users sending messages between them. Message number per user should not be big.

Another requirement is that all users will be able to talk to ...

Hi all,

I am keep getting the below in the SFS log file.

[ FINE ] > User [ java.nio.channels.SocketChannel[closed] ] removed

Can someone please explain what is this and if this message is a common message the SFS sends.

BTW - SFS linux and Windows 1.6.6, same behavior, lots of these in the log ...

We also tried sending a message to self every x seconds, this seemed to have the same effect on the idle time out. We have made a test where we changed the idle timeout to 2 min and sent a message to self every 30 seconds. After 2 minutes the user was thrown from SFS.

Another one we saw was that ...

both set for 1 hour, 3600 seconds

The message I get is:

User [ USER_NAME] removed

We also ran test as follows:
Setting the idle time out to 60 seconds
connect with a client that will send a message to himself every 30 seconds

We assumed the message will start calculating the idle timeout with each message (since the user was not ...

I still need to apply 1.6.9 to flash client side, but updating the server only did not solve the problem.

What is the best way to keep the TCP connection open, are there any recommendations?

Thanks

Hi,

We have a SmartFox server and Flex based clients that randomly disconnect from the SmartFox Server. In the SmartFox Server log we just see user [xxx] was removed. the clients start disconnecting a few minutes after they connect to the SFS server.

We are using Flex client API and SFS 1.6.6. WE ...