PJ41262: ADD CONFIGURATION FOR TIME THAT COMPONENT MANAGER WAITS TO RE-SEND WORK TO BUSY WORKER

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • If a component adaptor is busy, in PE 5.0.0.4 and earlier
    releases, the Component Manager dispatcher waits 30 seconds for
    adaptor to be ready.
    The 30 second wait was hard coded and the dispatcher would wait
    the full 30 seconds even though adaptor may have been ready to
    process more work sooner that 30
    seconds. Customer requested that the wait time be configurable
    in Milliseconds.
    
    Instead of 30 seconds, the system property,
    filenet.pe.cm.adaptor.dispatcher.nextworker.wait.interval.ms,
    can be used to configure the sleep time of the dispatcher when
    it waits for a free worker thread.  The default is 5000ms (5
    seconds).
    
    This JVM system property can be set for a specific component
    manager instance or all instances:
    
    1.  For a specific instance, specify the
    -Dfilenet.pe.cm.adaptor.dispatcher.nextworker.wait.interval.ms
    in the JRE Parameters located in the Advanced tab of the
    component manager instance GUI.
    
    2.  For all instances, create a text file,
    p8bpmsystems.properties in the <JRE>\lib directory of the JRE
    used by the component manager instances.  This file should
    contain the property name and value, as illustrated below
    
    filenet.pe.cm.adaptor.dispatcher.nextworker.wait.interval.ms=<#
    of ms>
    
    When both are specified, the value in the JRE Parameters takes
    precedent.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users who using this function                                *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply 5.0.0.6-P8PE-FP006 or newer                            *
    ****************************************************************
    

Problem conclusion

  • Fixed in 5.0.0.6-P8PE-FP006 and newer
    

Temporary fix

Comments

APAR Information

  • APAR number

    PJ41262

  • Reported component name

    PROCESS ENGINE

  • Reported component ID

    5724R7607

  • Reported release

    500

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-05-23

  • Closed date

    2014-05-05

  • Last modified date

    2014-05-05

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

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

    PJ41285

Fix information

  • Fixed component name

    PROCESS ENGINE

  • Fixed component ID

    5724R7607

Applicable component levels

  • R500 PSY

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

Case Foundation
Process Engine

Software version:

500

Reference #:

PJ41262

Modified date:

2014-05-05

Translate my page

Machine Translation

Content navigation