JR44371: CMVC 224428 - Enhance the SendTransactedMsg job to add a maxSeconds parameter to help control concurrency.

7.0.0-WS-WCServer-FP009
WebSphere Commerce Version 7.0.0.8 Fix Pack
WebSphere Commerce Version 7.0.0.9 Fix Pack

APAR status

• Closed as program error.

Error description

• The SendTransactedMsg scheduler job can run a long time when
  there are many messages to process.  When the job runs longer
  than the scheduled job interval, multiple instances of the job
  can run concurrently.  Each running job uses a scheduler thread.
  A way to effectively limit the number of concurrently running
  SendTransactedMsg jobs will help avoid associated resource
  contention.
  

Local fix

• The existing job parameter numOfMessages can be used to limit
  the concurrency by specifying a maximum number of messages to be
  processed by each job.
  

Problem summary

• USERS AFFECTED:
  WebSphere Commerce customers with many messages to be sent via
  the SendtransactedMsg scheduler job, as is normally the case
  when Sterling Commerce integration is used.
  
  PROBLEM ABSTRACT:
  Enhance the SendTransactedMsg job to add a maxSeconds parameter
  to help control concurrency.
  
  BUSINESS IMPACT:
  One case of impact: For customers using IBM Order Management
  Server integration with WebSphere Commerce they may be limited
  in the order transfer throughput that they want to achieve for
  their system. Higher order transfer throughput is possible by
  controlling the concurrency of the SendTransactedMsg job which
  the maxSecond parameter addresses.
  
  RECOMMENDATION:
  

Problem conclusion

• A new maxSeconds parameter allows you to specify the maximum
  number of seconds the SendTransactedMsg scheduler job should run
   for.  You can use this parameter to control how many
  concurrently executing instances of the job can run.  For
  example, if the scheduler job interval is set to 300 seconds,
  and the maxSeconds parameter is set to 800, then at most 2
  (800/300) instances can be running concurrently, since the first
   job will complete before the third job starts.
  
  -------------------------------------------------------------
  The latest available maintenance information can be obtained
  from the Recommended Fixes for WebSphere Commerce technote:
  

Temporary fix

• The existing job parameter numOfMessages can be used to limit
  the concurrency by specifying a maximum number of messages to be
  processed by each job.
  

Comments

• 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

  WC BUS EDITION

• Fixed component ID

  5724I3800

Applicable component levels

• R700 PSY

     UP