We'll try that and deploy it to production. Hopefully, the next time the issue occurs, we'll be able to catch the Exception and take appropriate action to correct the issue.

Thank you

I think you need to better debug your server side code, the behavior you're describing makes little sense and suggests that something else is going on. We've added traces before and after the code block, and in the case that I've mentioned the traces after the code block don't get output in the log...

What is not clear to me is how your userMap works. Does it contain custom IDs that are generated by you? If so they won't work with the getUserById() method because every user object already has its own auto-generated userID. Yes, I understand that. We're passing userId which is the SFS generated I...

We're using the following code to retrieve the user object of a logged-in player Integer userId = userMap.get(playerId); User user = null; if(userId !=null && userId != -1){ user = getApi().getUserById(userId); if(user != null) getApi().joinRoom(user, getParentRoom(), null, true, null, true,...

Hi, I am sending an extension command to a client using the send() method of the BaseClientRequestHandler class. On getting the response dump at the client's end, the trace was as follows: (utf_string) forRmId: 768 (utf_string) msgStr: Data is unavailable (utf_string) _cmd: levelProgressInfoResp The...

We've been using the Socket Policy Server provided by you at this link: http://www.smartfoxserver.com/download/get/42 for a couple of years now. Until last week, we've never had any issue with it. But since 13th December, 2016 (since the Flash player 24.0.0.x update was pushed), we've seen that ther...

So, we managed to solve the issue. The first problem was that we were using an old version of the SFS2X Java client API. So, we downloaded the latest API and tried to use it. Then, we learned that we need to use Java 1.7 instead of Java 1.6 which is what we were using. We updated Java and everything...

Can you provide us with the test application that you've written? We'd like to compare the code with ours and see what we're doing differently.

Even that didn't work. We're still getting the logs.

This is the code that we use to connect:


We're not using ConfigData object to connect.

We've already used set the debug flag as false in the code. But we're still getting the logs that I've mentioned. The other SFS logs are not printed, but only those lines still keep getting printed.

We are getting these logs printed frequently whenever we use the client and it hampers ours debugging effort since it creates an unnecessary clutter among the logs that we need to debug. Handling Header Size. Length: 376 (small) 14:53:55,583 INFO [sfs2x.client.core.SFSIOHandler] (New I/O worker #1) ...

So, are the answers in these threads incorrect, then?

viewtopic.php?f=18&t=14426
viewtopic.php?f=18&t=13981
viewtopic.php?f=18&t=9369

Cool. Thanks

As per my understanding (I think I might have read this written somewhere in the docs), when sfsApi().removeRoom() is called, the SFS removes the room only if there is no user currently joined in the room. So, based on that assumption, I executed the following code: int roomId = room.getId(); trace(...