FMSGuru

Hello,

We have build an online bingo game using FMS including chat functionality etc.
We didn't run into any problems while testing it on our local machines and on our test environment (which is located on the same server as our production environment).

Now it's on our live website and I am running into the following problem:
While playing the bingo, the FMS sometimes suddenly closes the connection (even when the bingo .swf is still running in my screen) and I don't really know why.

The FMS is constantly sending messages and Shared Objects to the clients. The only communication from client side to the FMS is when someone enters something in the chat.

So the only thing I can think of is: When nobody is chatting, the FMS doens't get any data from the client side and may think the Client is inactive and closes the connecting.
When more people are playing, the FMS doesn't close the connection (it seems).

FYI: There is one difference between our test environment and production/live environment . The live environment uses SSL and is loading the .swf on a https page.

EDIT: We bought a FMS 4.5 Interactive Server License, running on Windows Server 2008 x64
EDIT2: There are no errors in the logs (checked all of them). All I get is: "NetConnection.Connect.Closed"

Hope I made my problem/question clear.
Anyone any idea why FMS closes the connection?

Thanks in advance,
Tristan from the Netherlands
* Last updated by: Trist01 on 7/17/2012 @ 3:35 AM *

Did you try adjusting the timeout settings in the Application.xml file?

Hi Nikeah,

Thank you for your answer. I just changed some settings, not sure if it will solve our problems looking at the description of each Timout Setting. But it's worth a try!

I will come back here with the results.

Thanks.

Hi Nikeah,

Back here with the results. First is seemed to work. The bingo rooms were up for about 2-3 hours. But then it closed the connection again. At that time 2 players where playing and chatting in that bingo room. Any other ideas?

Thanks,
Tristan

The access.log/ core.log should show if the client was disconnect since it was idle. You might need to increase the log level to see it if you are not already seeing this.
Have you tried disabling AutoCloseIdleClients in Application.xml. Or may be changing MaxIdleTime.
<AutoCloseIdleClients enable="false">
<MaxIdleTime>3600</MaxIdleTime>
</AutoCloseIdleClients>

The other thing to try out would be keep sending some keep-alive message from client to the server.

Hi Gsehgal,

Thank you for your answer. Unfortunately this also does not work for us.
Now I did find something in the logs (edge log):

2012-07-20 02:39:55 1704 (i)2581250 Edge disconnected from core (3724). -
2012-07-20 09:03:10 1704 (i)2581252 Registering core (5296). -
2012-07-20 09:03:43 1704 (i)2581252 Registering core (3888). -
2012-07-20 09:35:32 1704 (i)2581250 Edge disconnected from core (5296). -
2012-07-20 09:46:15 1704 (i)2581252 Registering core (2984). -
2012-07-20 09:52:08 1704 (i)2581250 Edge disconnected from core (2984). -
2012-07-20 09:52:08 1704 (i)2581250 Edge disconnected from core (3888). -

I think this is exactly the cause of the problem. "Edge disconnected from core".
When I looked for this on Google I found something about RAM memory, but that certainly is not the problem.
How and when is this happening?

Does it maybe have something to do width intstances? My application is called 'bingo' and the instances are numbers (1 to 3) which indicate the 'RoomID'.

EDIT: At the same time, this is what the master log says:

2012-07-20 09:35:33 2096 (i)2581223 Core (5296) is no longer active. -
2012-07-20 09:35:33 2096 (w)2581256 Core (5296) _defaultRoot_:_defaultVHost_:::_0 experienced 1 failure[s]! -
* Last updated by: Trist01 on 7/20/2012 @ 2:04 AM *

Ok, this means the FMSCore is crashing. As you mentioned the issue is reproducible only on production systems, hence it would be difficult for me to analyse further without looking in to core dump.
If you are using windows build then generate the core dump using adplus. Just let the following command run and when ever the core crashes you should get a dmp.
ADPlus -crash -pn FMSCore.exe -o c:\temp
Refer: http://support.microsoft.com/kb/286350
I am not sure how you will share the dump over this forum but you can email me the ftp details at gsehgal@adobe.com and share the logs and core dump.

Thanks again gsehgal, currently installing ADPlus. Will come back to you with the results.

Hi,

AdPlus has not placed any memory dumps in the c:\temp folder I made. Am I doing something wrong? The FMS problem is still there and I can still see the failures in the FMS logs.

See this screenshot of how I set up AdPlus:

I see the screenshot is not completely shown, view it here.

Thanks
* Last updated by: Trist01 on 7/25/2012 @ 2:12 AM *

Hello,

We are still having the same problem.

We have 2 applications running, called: bingorooms and bingo

bingorooms always runs in the instance called 1, so thats bingorooms/1

We have 4 bingo applications running:
bingo/1
bingo/2
bingo/3
bingo/4

We use the instance name as an ID to get the right data for a bingo room.
bingo/3 and bingo/4 have no problems at all and they are up and running all the time.

bingo/1 and bingo/2 (and also bingorooms/1) keep getting connection errors.
Is there something about instances I don't understand? Maybe I do not use them in the right way...

Tristan

Hello,

Problem still there - not solved.
Anyone any idea?

Thanks

As you mentioned adplus didnt dump anything for you. Can you please try following command i.e. running the vb script of adplus. This script will wait till the core crashes and will take a dump for you.
cscript adplus.vbs -crash -pn FMSCore.exe -o c:\temp

Another way to validate adplus is working for you please take a hang dump of the process.
cscript adplus.vbs -hang -p <pid of process> -o c:\temp