Release Automation

Action Type: Run Command Line (Property 'Time Out Duration")

We observed that some servers reacts very slow to below command line action. sometimes took more than 20 minutes to output for below query.

CMD: { wmic product where "name like '%QFramework%'" get version }

Since the Automated process don't have to wait until this action finish, we have implemented time out duration for the action type 'Run Command Line' (please refer the attachment). Although we have set timeout duration the action keeps on running for infinite time. Ideally specking the action should fail after time out duration so that we can manfully pass\resume it and let the automation progress to next flow. 

Please suggest since the action is not failing after time out duration.

Hi

I did do a quick test and i got the following result . What RA version are you using and on which OS.

-

Regards

Dirk

Hello Dirk,

Thanks for the response. we are using CA RA "Version: 6.3.0.9622". OS: WINDOWS.

we are especially interested in below command.

WMIC product where "name like '%QFramework%'" get version

We observed that some of our windows servers reacts very slow to above command. Sometimes took more than 20 minutes to output for above command.

Since the Automated process don't have to wait until this action finish, we have implemented time out duration for the action type 'Run Command Line' (Please refer the attached image of our action). Although we have set timeout duration the action keeps on running for infinite time. Ideally specking the action should fail after time out duration so that we can manfully pass\resume it and let the automation progress to next flow. 

Please suggest since the action is not failing after time out duration.

Thanks,

Nikhil

Hi,

My understanding is "Time Out Duration" doesn't mean to abort the action.

The value is used to check if the action takes too long time to complete despite the command returns. So, we need to wait to complete the process. 

For example,  (on Windows)

• Time Out Duration: 30
• Command Line String: notepad.exe

If notepad.exe process is killed within 30 seconds, the result is succeeded.

If notepad.exe process is killed after 30 seconds or more, the result is failed.

In both case, the action is running till killing notepad.exe manually.

I'm not sure that QFramework (you mentioned) uses Windows registry, but if so, you can "reg export <key name> <file name>" instead of wmic command. I expect it is better response.

Thanks

Yas

We have seen issues where the Run Command line action does not automatically fail after the timeout duration passes as well. Especially when calling scripts that may be hung on a nested process. 

Hi

I tested this with your command and this was the result .

So the command action should fail , if this does not occur on your installation , i would suggest to raise a support case

so we can investigate the logs .

The agent version or java version could play a role in this .

Regards

Dirk

Hi
I believe your questions has been answered, I will mark this as the correct answer.
When your question is not answered or you still have additional questions please let us know.
With Kind Regards

Dirk