Troubleshooting: Job Kill Issues

If a kill on an RA JD Edwards Agent Job fails, the Job will remain in the Activities dialog and be monitored until it completes in JDE. Once it has finished, the Job report will show that a kill was attempted but failed and will show information about why it failed.

When a Kill Cannot Reach the JDE Server

If a kill fails because it cannot reach the JDE server to execute the Business Function there will be an error similar to this in the report:

2010-07-08 10:11:18            kill of job has been requested by user

2010-07-08 10:11:18            Error executing kill job business function

2010-07-08 10:11:18            Call to JDE failed:Unknown Host: XX-VWADEV08 Could not contact JDE server. Check server name and port.

If you see errors like these, check the JDE Server name and Port specified in the Agent panel.

When a Job is not in a Killable Status

If the Job cannot be killed because it's in a status that does not allow kill or because the Job is not running in JDE there will be messages like the following:

2010-07-12 09:48:15 JDE job number 111 was not found. Job does not exist in the JDE system.

2010-07-12 09:48:15 Job has finished in the JDE system. Status:Done (D). Terminate job was not executed

2010-07-12 09:48:15 Job is not running in the JDE system. Status:Waiting (W). Terminate job was not executed

No JDE Jobid. Job has not been started at JDE.

When the JDE Business Function Returns an Error

If the JDE Business Function returns an error you will get a message similar to this, including the XML response from the Business Function.

2010-07-15 13:15:04            Kill of job has been requested by user

2010-07-15 13:15:17            Error executing kill job business function

2010-07-15 13:15:17            Kill execution return code:0

2010-07-15 13:15:17            Business function return code:130T

2010-07-15 13:15:17            Error text:Error: Action Failed

2010-07-15 13:15:17            server:vwadev08 port:6015

2010-07-15 13:15:17            execHost:vwadev08 execPort:6015 env:JDV900 queue:QBATCH

2010-07-15 13:15:17            XML returned:<jdeResponse role="*ALL" pwd="pass" environment="JDV900" type="callmethod" session="29971.1279224914.1" user="JDE">

2010-07-15 13:15:17              <callMethod app="JavaApp" name="TerminateJob">

2010-07-15 13:15:17                <returnCode code="0"/>

2010-07-15 13:15:17                <params>

2010-07-15 13:15:17                  <param name="szExecutionhostname">

2010-07-15 13:15:17                    vwadev08

2010-07-15 13:15:17                  </param>

2010-07-15 13:15:17                  <param name="szPortNumber">

2010-07-15 13:15:17                    6015

2010-07-15 13:15:17                  </param>

2010-07-15 13:15:17                  <param name="szJobQueue">

2010-07-15 13:15:17                    QBATCH

2010-07-15 13:15:17                  </param>

2010-07-15 13:15:17                  <param name="szQueueType">

2010-07-15 13:15:17                    01

2010-07-15 13:15:17                  </param>

2010-07-15 13:15:17                </params>

2010-07-15 13:15:17                <errors>

2010-07-15 13:15:17                  <error code="130T">

2010-07-15 13:15:17                    Error: Action Failed

2010-07-15 13:15:17                  </error>

2010-07-15 13:15:17                </errors>

2010-07-15 13:15:17              </callMethod>

2010-07-15 13:15:17            </jdeResponse>

In the cases where the Business Function fails, you should also check the JDE Server log for more information.