webserver number of running instances

Question

question

daniela.z asked May 31 2016 at 7:42 PM Ben Wilson commented Jun 07 2016 at 8:10 PM

webserver number of running instances

We are having issues starting more than 5 model instances, causing the API to return the fail message:

The FlexSim webserver stops responding from that point on. Currently the way we solve this issue is by re-starting the server, all instances go away and the site comes backup. In the webserver configuration file we changed the number of “Max Instances of Flexsim” to 20 from the default 8, but we are still having the same issue.

Are there any other configuration settings that we need to change?

Software Version:

FlexSim 16.0.1

webserver api server configuration instance

image001.png (10.8 KiB)

· 6

Phil BoBo ♦♦ commented · May 31 2016 at 7:57 PM

Can you open more than 5 instances of FlexSim with the model you are trying to open regularly (without using the webserver)? Can your hardware support opening that many FlexSim instances with that model open? Do you have enough RAM?

1 ·

daniela.z Phil BoBo ♦♦ commented · May 31 2016 at 8:21 PM

Yes, we can run more than 5 instances using the desktop app but not using the webserver. We updated our hardware to handle several instances so that shouldn't be a problem.

0 ·

Ben Wilson ♦♦ daniela.z commented · Jun 01 2016 at 1:50 PM

I wonder if the server overhead diminishes what the server is capable of.

Question: can you launch more than 5 instances if you do not connect to them?

1 ·

Ben Wilson ♦♦ commented · Jun 01 2016 at 1:54 PM

I'm surprised you would need to restart the entire machine. If you have desktop access to that server, can you check if it is the entire operating system frozen, or is it just the server software (IIS or Apache) that is frozen?

If the latter, you should only need to restart the server software, not the whole computer.

Perhaps it is not the server software, but some aspect of FlexSim that is crashed? Not sure how that would work from the server itself since it is just a DLL that that your server software attaches to. What about the individual FlexSim instances running - are they the thing that freezes?

I guess this whole comment boils down to: What exactly is freezing/crashing/not responding? Could you be more specific about the failure situation?

1 ·

daniela.z Ben Wilson ♦♦ commented · Jun 01 2016 at 2:06 PM

The situation is that after starting 5-6 instances the Flexsim webserver will not create any more instances and returns the message: capture.png

At that point I have to terminate all instances to be able to start new ones.

0 ·

capture.png (11.3 KiB)

victoria.davila commented · Jun 01 2016 at 4:03 PM

So to provide some clarification on the issue:

The FlexSim webserver is unable to create a new instance after creating 5 instances (error occurred on 5/31). Today on 6/1 the webserver was unable to create a new instance after successfully creating 4 instances. The instances successfully started are still running despite the error. In order to start a new instance we have to terminate one that is currently running. Currently we are not restarting the server or machine itself to restart new instances, only terminating ones that are already running. In the webserver configuration file we changed the number of “Max Instances of Flexsim” to 20 from the default 8, but we are still having the same issue. It appears the FlexSim webserver itself is not responding.

2016-06-01-11-27-52.jpg

0 ·

2016-06-01-11-27-52.jpg (34.3 KiB)

______

Cookie preferences

Your privacy is important to us and so is an optimal experience. To help us customize information and build applications, we collect data about your use of this site.

May we collect and use your data?

Learn more about the Third Party Services we use and our Privacy Statement.

Strictly necessary – required for our site to work and to provide services to you

These cookies allow us to record your preferences or login information, respond to your requests or fulfill items in your shopping cart.

YES

Improve your experience – allows us to show you what is relevant to you

These cookies enable us to provide enhanced functionality and personalization. They may be set by us or by third party providers whose services we use to deliver information and experiences tailored to you. If you do not allow these cookies, some or all of these services may not be available for you.

YES

NO

Customize your advertising – permits us to offer targeted advertising to you

These cookies collect data about you based on your activities and interests in order to show you relevant ads and to track effectiveness. By collecting this data, the ads you see will be more tailored to your interests. If you do not allow these cookies, you will experience less targeted advertising.

YES

NO

Are you sure you want a less customized experience?

We can access your data only if you select "yes" for the categories on the previous screen. This lets us tailor our marketing so that it's more relevant for you. You can change your settings at any time by visiting our privacy statement

Your experience. Your choice.

We care about your privacy. The data we collect helps us understand how you use our products, what information you might be interested in, and what we can improve to make your engagement with Autodesk more rewarding.

May we collect and use your data to tailor your experience?

Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.

Answer 1 · 2016-06-02T22:16:13Z

Ben Wilson answered Jun 02 2016 at 10:16 PM Ben Wilson commented Jun 07 2016 at 8:10 PM

There is a Windows Registry setting that limits the amount of memory (desktop heap size) that Windows will allocate for non-interactive processes. Here is the registry path:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\SubSystems\Windows

This key has a value that is a long string with more key/value pairs:

%SystemRoot%\system32\csrss.exe
ObjectDirectory=\Windows
SharedSection=1024,20480,512
Windows=On
SubSystemType=Windows
ServerDll=basesrv,1
ServerDll=winsrv:UserServerDllInitialization,3
ServerDll=sxssrv,4
ProfileControl=Off
MaxRequestThreads=16

The SharedSection key defines, in its 3rd "parameter", the memory quantity we're talking about. By default it may be 512 or 768 (512 in the example above). You need to increase this beyond the total amount of memory that all your instances will use simultaneously.

In my testing, I increased the size to 1536. When doing so, I was able to launch more instances, until the total memory usage of my instances was 1125. Then I increased the registry to 4096, and was able to launch 3030 worth of FlexSim instances. Finally I increased the memory to 8196 and was able to hit all 20 instances allowed by the configuration file.

Keep in mind this was just my sample model, your model may require more memory. Also, I wasn't running my instances. If they were running, they would take more memory.

In my testing, FlexSim was able to use up about 70-75% of the desktop heap size memory that I specified in the registry. The rest is still used by Windows or other processes, so do plan on some overhead not associated with FlexSim.

This Microsoft article describes what is going on. In particular, search the article for 'SharedSection' for more information.

After changing the 3rd part of SharedSection, you will need to reboot for the change to take effect.

· 1

question