AppManage exit codes are usually zero or negative values. Why would a positive exit code value returned?
Article ID: KB0094443
Updated On:
| Products | Versions |
|---|---|
| TIBCO Runtime Agent (TRA) | - |
| Not Applicable | - |
Description
Resolution:
AppManage returns '0' for success or a negative value for failure. If a positive value is observed, then consider investigating the following possibilities.
1). Some automation tools that wrap around AppManage, the likes of ANT, Autosys, etc., may display the returned code as an unsigned one byte value:
-1=255, -2=254,..., -110=146
2). Sometimes the code might come from the OS when it has to terminate the job due to diverse abnormal conditions such as insufficient resources. This is not limited to AppManage. The following shows some of the possible code values that can be seen in a Unix environment:
9: Ran out of CPU time.
64: The framework ended the job nicely for you, most likely because the job was running out of CPU time. But it means you did not go through all the data requested. The solution is to submit the job to a queue with more resources (bigger CPU time limit).
125: An ErrMsg(severe) was reached in your job.
127: Something wrong with the machine?
130: The job ran out of CPU or swap time. If swap time is the culprit, check for memory leaks.
131: The job ran out of CPU or swap time. If swap time is the culprit, check for memory leaks.
134: The job is killed with an abort signal, and you probably got core dumped. Often this is caused either by an assert() or an ErrMsg(fatal) being hit in your job. There may be a run-time bug in your code. Use a debugger like gdb or dbx to find out what's wrong.
137: The job was killed because it exceeded the time limit.
139: Segmentatation violation.
140: The job exceeded the "wall clock" time limit (as opposed to the CPU time limit).
3). The controlled application, such as the TIBCO BusinessWorks (BW) engine, returned a code that AppManage did not understand, and AppManage is simply passing this code through. This is a rare occurrence.
AppManage returns '0' for success or a negative value for failure. If a positive value is observed, then consider investigating the following possibilities.
1). Some automation tools that wrap around AppManage, the likes of ANT, Autosys, etc., may display the returned code as an unsigned one byte value:
-1=255, -2=254,..., -110=146
2). Sometimes the code might come from the OS when it has to terminate the job due to diverse abnormal conditions such as insufficient resources. This is not limited to AppManage. The following shows some of the possible code values that can be seen in a Unix environment:
9: Ran out of CPU time.
64: The framework ended the job nicely for you, most likely because the job was running out of CPU time. But it means you did not go through all the data requested. The solution is to submit the job to a queue with more resources (bigger CPU time limit).
125: An ErrMsg(severe) was reached in your job.
127: Something wrong with the machine?
130: The job ran out of CPU or swap time. If swap time is the culprit, check for memory leaks.
131: The job ran out of CPU or swap time. If swap time is the culprit, check for memory leaks.
134: The job is killed with an abort signal, and you probably got core dumped. Often this is caused either by an assert() or an ErrMsg(fatal) being hit in your job. There may be a run-time bug in your code. Use a debugger like gdb or dbx to find out what's wrong.
137: The job was killed because it exceeded the time limit.
139: Segmentatation violation.
140: The job exceeded the "wall clock" time limit (as opposed to the CPU time limit).
3). The controlled application, such as the TIBCO BusinessWorks (BW) engine, returned a code that AppManage did not understand, and AppManage is simply passing this code through. This is a rare occurrence.
Issue/Introduction
AppManage exit codes are usually zero or negative values. Why would a positive exit code value returned?
Feedback
Yes
No
Powered by
