When invoke a batch file by using the Custom:execute on Windows, it says succeed but some command did not get executed, why?
Article ID: KB0086776
Updated On:
| Products | Versions |
|---|---|
| TIBCO Hawk | - |
| Not Applicable | - |
Description
Resolution:
It’s really possible that there are too many commands in the batch file and some of them generate too much output. As our document pointed out:
If a Custom::execute is performed, the TIBCO Hawk agent does not wait for the return value and the parent process persists in stdout or stderr. These processes do not terminate or time out and eventually use up the system resources. To avoid this, redirect stdout and stderr to NUL. For example:
- On Microsoft Windows, where 1 is stdout, and 2 is stderr:
c:\<process>.bat 1> NUL 2> NUL
- On Unix:
<process> > /dev/null
Please follow this suggestion and see if this issue gets resolved.
Issue/Introduction
When invoke a batch file by using the Custom:execute on Windows, it says succeed but some command did not get executed, why?
Feedback
Yes
No
Powered by
