I've been experimenting with the System caller to run third party command line tools. It works great for the most part, however, when you stop the workspace the called process keeps running.
It would be nice if the call could be killed/cancelled when the FME process is aborted.
The problem is compounded when the sub process leverages the folder created by the TempPathNameCreator - If the FME process is aborted then these files do not get cleaned up.
Idea comes from this QA: https://knowledge.safe.com/questions/87473/process-triggered-from-system-caller-does-not-end.html
Archived
Process started by the SystemCaller should end if workspace is aborted
+47- Celebrity
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+2It would also be great to have more info why a process keeps running.
More logging info needed!
Login to the community
No account yet? Create an account
An FME Account is required to contribute
LoginEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.