Working instances

Main Forum
1

Hello,

The limit for simultanously working instances on a single license is 4. Why the system gives me the message saying I've reached the limit when there're only two instances working?

Best regards
Dobrochna

2

Hi Dobrochna,

That is very strange. One case in which this can happen is if you close an instance and restart AnyBody immediately. In this case, there is some time that must pass from the moment you close the instance to the time it is actually cleared from the working memory (because deletion of model from the memory takes some time). Depending on the model, it can be a few seconds. You can, of course, see that in the Task Manager, where you should be able to see all the running instances of AnyBody. Can you let me know what license type you are working with and what error message you are seeing? You are welcome to write to support(at)anybodytech(dot)com

Best regards,
Dave

3

Hi Dave,

So the situation was pretty strange cause I was working with 4 instances at the very beggining. Then I turned off one of them and after that, the message started to show up every time I wanted to start the fourth instance:
"The maximum number of licensed AnyBody Modeling System instances are already running. If you want to start more instances of AnyBody, please close any unused instances first or import another valid licesne. Each valid AnyBody license allows 4 concurrently running instances of AnyBody."
A few days later I had to turn off one of three instances I was working on and the same thing happened. The message started to appear when I tried to start the third instance. this situation was constant for a few days when I decided to start this topic here.

The Task Manager was always showing only the instances I was actually using.

When I tried to use AnyBody from the console or with Python, the same message was showing.

The situation changed recently, after a major computer restart. Now I can use all 4 instances, so let's say the problem is fixed. However, I decided to decsribe the issue since maybe someone will have the same problem.

Nevertheless, thank you very much for the response.
I'm currently working on a non-faculty research permanent license.
Do you know what could cause this problem?

Best regards
Dobrochna

4

Hi Dobrochna,

That is indeed strange. It sounded like somehow AnyBody was not closing properly and it's hard to say if it's an AnyBody issue, or some other issue. If you are able to reproduce this behavior, we would be glad to investigate it further.

Now, are you able to exit AnyBody and start again without your license getting blocked by an instance that you closed already?

Best regards,
Dave

5

Hello Dave,

So unfortunatelly I still don't know what triggers the issue but it happened at least twice since my last message here. Each time the computer restart solved the problem. I may try to identify it next week, since I have some urgent analyses to run for a few days now. I'll bring here some info if I succede in reproducing the scheme.

Thank you for your interest.

Best regards
Dobrochna

6

Hi Dobrochna,

I am sorry to read that. This is definitely something that we would like to understand and identify the cause.

Are you running your simulations through Python, using a script for batch processing your trials? Or do you see the issue when you work with the GUI version of AnyBody?

Best regards,
Dave

7

Hi Dave,

So I encountered the issue again and it seems the error appears when the GUI instances are working continuously for several hours. Don't know the exact needed time, but about 24 hours was enough. Also don't know if it's universal for different systems. I'm working on Windows 10 pro via a remote desktop.

I'll check soon and let you know if the Python path shows the same scheme.

Best regards,
Dobby