PH56574: BATCH CODE BUG WHICH IS CAUSING A LOOKUP FAILURE AND SUBSEQUENT RETRY(S)

APAR status

• Closed as program error.

Error description

• [8/11/23 9:30:40:587 EDT] 000000a9 3 UOW=
  source=com.ibm.ws.batch.JobSchedulerMDB org=IBM prod=WebSphere
  component=Application Server thread=[MessageListenerThreadPool :
  0]
           com.ibm.ws.batch.JobSchedulerMDB.init catch
  NameNotFoundException. Trying to lookup again. Retry # 1
  

Local fix

• Customer was able to resolve the issue by performing the
  following:
  Fully delete the cluster, uninstall the Job Scheduler and MDILP
  component ( -remove installWSGridMQClientMode.py script to
  remove).  Upon rebuilding and reinstalling all components
  everything seems to work correctly now.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  *                  Java Batch                                  *
  ****************************************************************
  * PROBLEM DESCRIPTION: When a batch job is submitted using the *
  *                      WSGrid external client to a Job         *
  *                      Scheduler, the job does not execute and *
  *                      there is what appears to be a           *
  *                      MessageListenerThreadPool hung thread.  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When a Java Batch Job Scheduler has been configured to use the
  WSGrid external scheduler interface for submitting jobs, there
  is a system app Message Driven Bean (MDB) involved which
  accepts incoming messages from the external client.
  When this MDB initializes on startup, it attempts to perform a
  remote lookup on the JobScheduler home interface.
  If this initial lookup fails, the operation will be retried.
  If a subsequent retry succeeds, a code bug is preventing the
  initialization from proceeding, and the lookup loop will
  continue.
  

Problem conclusion

• A code update has been made to properly continue after a
  successful Job Scheduler remote lookup has been made.
  
  The fix for this APAR is targeted for inclusion in fix pack
  8.5.5.25 and 9.0.5.18. For more information, see 'Recommended
  Updates for WebSphere Application Server':
  https://www.ibm.com/support/pages/node/715553
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels