IJ19778: CRONTASKS STOP SENDING OR RECEIVING MESSAGES FROM SEQUENTIAL JMS QUEUES

APAR status

• Closed as program error.

Error description

• PROBLEM:
  The JMSQSEQCONSUMER Crontasks stop processing inbound
  and outbound messages in the JMS queues intermittently. The
  IFACETABLECONSUMER crontasks may stop retrieving messages from
  the interface tables. Other crontasks are also affected. The
  cron simply stops, and no errors are produced whatsoever.
  The
  taskscheduler table may or may not show that the LASTRUN
  date/time is later than the LASTEND date/time, but this is not
  true much of the time.
  
  PERFORMANCE ISSUE: N
  
  STEPS TO
  REPRODUCE:
  Not reproduced as no steps exist to cause this issue
  to occur.
  
  RESULTS:
  The crontasks stop intermittently and will
  not restart.
  
  EXPECTED RESULT:
  Crontasks should continue restart
  on their scheduled intervals.
  
  PRODUCT VERSION:
  Maximo Asset
  Management 7.6.1
  

Local fix

• Connect to your database using a SQL developer tool, and run the
  following select statement:
  
  select * from taskscheduler where
  taskname='your crontask.instance name';
  
  Note the value in the
  SERVERNAME column associated with the crontask instance that
  will not run.
  
  Delete the entry from the taskscheduler
  table:
  
  delete from taskscheduler where taskname='your
  crontask.instance name';
  commit;
  
  Restart only the JVM noted in
  SERVERNAME column from the select statement results above.
  
  The
  crontask instance will automatically resume.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * MAXIMO                                                       *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * CRONTASKS STOP SENDING OR RECEIVING MESSAGES FROM SEQUENTIAL *
  * JMS QUEUES                                                   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• The fix for this APAR is contained in the following maintenance
  package:
  	 | release\fix pack | Interim Fix for Release 7.6.1.2 Product
  

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

  MAXIMO ASST MGM

• Fixed component ID

  5724R46AM

Applicable component levels