Problems running the batch container

Use this information to diagnose problems with the batch container

Missing prerequisites.

See the topic Prerequisites for the correct versions of software and service that must be installed. If the prerequisites are not met, then you could see these messages:
  • In the batch container log:
    Fri Apr 19 12:38:24 GMT 2013¨ 0 WARNING HeartBeater sendHeartBeat¨ Could not send heart beat to: 
    [CGHOST:CGPORT]/PGCProxyController/PortableGridContainerProxyServlet java.lang.NoSuchMethodError: com/ibm/cics/server/HttpSession.open(Z)V
  • In the JVM error log, either:
    java.lang.NoSuchMethodError: com/ibm/cics/server/HttpSession.open(Z)V
    OR
    com.ibm.ws.gridcontainer.exceptions.GridContainerServiceException: Batch: Message,Error File Not Found: batchcontainer-config.xml, not found or could not be formatted.
    Followed by:
    Caused by: java.io.FileNotFoundException: null/batchcontainer-config.xml (EDC5129I No such file or directory.)

Batch jobs run but stay in submitted state.

If the jobs that you submitted to the batch container are running, but stay in submitted state, check the batch log for errors:
WARNING [com.ibm.cics.batch.comms.StatusUpdateSender sendJobStatusUpdate] Could not send job status update[java.lang.Exception: No Queue found for scheduler: (actual server name the job has be run from) 

This problem occurs when the JobSchedulerInfo->Name (Cell/Node/Server) is wrong, but the host and port are correct. In this case, the batch container registers correctly, and you can still submit jobs that the batch container runs, but their state does not change.

Enter the correct information in the JobSchedulerInfo->Name and restart the job.



probs_container.html | Timestamp icon Last updated: Sunday, 4 June 2017