PJ40791: SINCE UPDATE TO EPROCESS 5.2.0-002, COMPONENT MANAGER PROCESSES SOME OPERATIONS TWICE.

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

  • Using Component Manager (CM) with multiple threads, users notice
    that work items get processed more than once.
    
    In some particular cases, the Component Manager threads are
    having the same work item (assuming with lock) at the same time,
    so they both process the same work item.
    Depending on how the task is defined and how fast it runs,
    eventually one thread finishes its task and another thread is
    still able to process the work item hence CM operation executed
    twice.
    
    This problem only happens when multiple threads are configured.
    And only
    with Event Port configured (as all threads will get notified at
    the same time when a new work item arrived in the CM Queue).
    This problem only happens with SQL Server 2008 and later.  Using
    SQL Server 2000 and 2005, this
    situation will not occur.
    
    The problem is with SELECT.  Given only one WobId arriving in
    the component queue, more than one thread will get the same
    WobId with lock.
    
    The work-around for now is to use single-thread.  With
    single-thread, you will not encounter this problem.
    or if you use multiple-threads do not configure the Event Port.
    There is a small chance (rare) you will get this issue w/o using
    the
    Event Port.
    

Local fix

  • Configure the CM to use a single-thread.  With
    single-thread, you will not encounter this problem.
    If you use multiple-threads do not configure the Event Port.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * 4.5.1 PE users                                               *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply 4.5.1.4-P8PE-FP004 or newer.                           *
    ****************************************************************
    

Problem conclusion

  • Fixed in 4.5.1.4-P8PE-FP004 and newer.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PJ40791

  • Reported component name

    PROCESS ENGINE

  • Reported component ID

    5724R7607

  • Reported release

    451

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-11-28

  • Closed date

    2013-06-13

  • Last modified date

    2013-06-13

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

    PJ40789

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

Fix information

  • Fixed component name

    PROCESS ENGINE

  • Fixed component ID

    5724R7607

Applicable component levels

  • R451 PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Case Foundation
Process Engine

Software version:

4.5.1

Reference #:

PJ40791

Modified date:

2013-06-13

Translate my page

Machine Translation

Content navigation