Had a hard time trying to let FME run out of memory, so I thought it would be faster to just ask around.
My guess is no, right? Since it usually says "Warning: not all FMESessions that were created were destroyed before shutdown. This may cause instability" in the log...
As far as I know:
not all FMESessions that were created were destroyed
...is just a generic catch-all message when something has gone wrong. We can't be more specific because it's an area of code that unexpectedly errors. If it occurs you should certainly let us know via our support team (safe.com/support) as it is a bug that needs fixing.
In this scenario the translation may stop, or it may complete. I would be careful to check the output in that case, but I've no evidence to say it will/won't be compromised.
In any case, it's not specifically a memory error.
Basically if the workspace errors out with an FME engine crash, or it fails with an error in the log, then I would not expect the Python script to execute.
If the workspace runs to completion, even if there is a message like that in the log, I would expect the Python script will execute.
Of course, I now stand to be corrected if you find an example that goes against this behaviour!
Mark
As far as I know:
not all FMESessions that were created were destroyed
...is just a generic catch-all message when something has gone wrong. We can't be more specific because it's an area of code that unexpectedly errors. If it occurs you should certainly let us know via our support team (safe.com/support) as it is a bug that needs fixing.
In this scenario the translation may stop, or it may complete. I would be careful to check the output in that case, but I've no evidence to say it will/won't be compromised.
In any case, it's not specifically a memory error.
Basically if the workspace errors out with an FME engine crash, or it fails with an error in the log, then I would not expect the Python script to execute.
If the workspace runs to completion, even if there is a message like that in the log, I would expect the Python script will execute.
Of course, I now stand to be corrected if you find an example that goes against this behaviour!
Mark
So you also expect that the Python shutdown script does not get executed when an out of memory issue occurs (I have personally never experienced that the workspace still ran to completion after that btw). How would you deal with this situation if the Python shutdown script contains code that writes some results to a database? This will never be written then...
So you also expect that the Python shutdown script does not get executed when an out of memory issue occurs (I have personally never experienced that the workspace still ran to completion after that btw). How would you deal with this situation if the Python shutdown script contains code that writes some results to a database? This will never be written then...
No, it's unlikely that a workspace will run to completion if a memory issue did occur, but it can run to completion and still show that "not all FMESessions" error right at the end, which is why I mention that possibility.
No, it's unlikely that a workspace will run to completion if a memory issue did occur, but it can run to completion and still show that "not all FMESessions" error right at the end, which is why I mention that possibility.
Of course, you guys don't aim for FME to crash and I have to say that it rarely ever runs out of memory. But I do have some occasions with SketchUp files that contain a lot of geometry instances. When I instantiate them (which you sometimes have to do at a certain point if you want to manipulate them), the memory consumption might explode. Sure, optimization of my workspace takes a bite off, but I believe that the main issue is that we run our engine on AWS EC2 (Windows). I have the impression that the engine thinks that there is way more memory available (e.g. all the memory on AWS) then there actually is... However, I will contact the FME Cloud team to ask how they dealt with this issue!