IJ04122: CRONTASKS THAT SEND EMAIL RESULTS USING MXE.EMAIL.CONTENT.TYPE TEXT/HTML MAY HANG AFTER PROCESSING THE RECORDS

APAR status

• Closed as program error.

Error description

• Cron tasks example pmwogen crontask, that send results via email
  using a mxe.email.content.type of text/html may hang after
  processing the records but before results of the cron task are
  emailed. The problem is in parsing the email message if the
  message is large. For example, after work orders are created for
  a site that has 5000 PMs via the PMWoGenCronTask, a message of
  ~10K lines is created but fails to be sent. Also, the cron task
  is unable to proceed onto the next site. The exact size of the
  message that will encounter this problem may vary depending on
  the jvm server specs.
  
  Steps to Reproduce
  
  1. Make sure in System Properties that mxe.email.content.type is
  null or explicitly set to text/html. The default is text/html
  so if it's null text/html is being used
  2. Identify a site that has a large number of PMs.
  3. In Organizations > PM Options:
  a) make sure that the site has 'Automatic PM WO generation'
  checked.
  b) make sure that E-mail Address Notification has a valid email
  address.
  4. Enable an instance of the PMWoGenCronTask.
  
  You will notice that the work orders for the site are generated,
  but the email is not sent and sites not processed prior to this
  site will not be processed by the cron task.
  

Local fix

• no work around
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Users with crontasks which send emails containing text/html. *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Crontasks which send send emails with content-type of        *
  * text/html may hang while processing the email message.       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• The fix for this APAR is included in the following package:
                          | Release 7.6.1.0 of Base Services.
  

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

  ADMINISTRATION

• Fixed component ID

  5724R46A1

Applicable component levels

• R760 PSY

     UP