IBM Support

IT13464: DATABASEINPUT NODE THREAD CAN SPIN CHECKING FOR NEW EVENTS WHEN ADDITIONAL INSTANCES ARE USED

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When a message flow with a DatabaseInput node has more
    available processing threads than events to process, one of the
    threads can repeatedly read the Events table looking for more
    events to process without a wait (equal to the polling
    interval) between each table read. This can occur if the
    threads processing the events take a long time to complete and
    call EndEvent, such that the thread reading the events
    table keeps reading the existing events that are already in the
    cache. This can cause excessive database selects.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of WebSphere Message Broker V8.0 and IBM Integration
    Bus v9.0 and V10.0 using the DatabaseInput node.
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When a message flow with a DatabaseInput node has more available
    processing threads than events to process, one of the threads
    can repeatedly read the Events table looking for more events to
    process without a wait (equal to the polling interval) between
    each table read. This can occur if the threads processing the
    events take a long time to complete and call EndEvent, such that
    the thread reading the events table keeps reading the existing
    events that are already in the cache. This can cause excessive
    database SELECT operations.
    
    There are a number of resource name changes between WebSphere
    Message Broker and IBM Integration Bus Version 9.0.  For details
    visit
    http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e
    tools.mft.doc/bb23814_.htm
    

Problem conclusion

  • The product now will wait for the polling interval if no new
    events were found during the last SELECT operation.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.8
    v9.0       9.0.0.6
    v10.0      10.0.0.5
    
    The latest available maintenance can be obtained from:
    http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
    
    If the maintenance level is not yet available,information on
    its planned availability can be found on:
    http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT13464

  • Reported component name

    WEB MESSAGE BRO

  • Reported component ID

    5724J0520

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-01-28

  • Closed date

    2016-05-25

  • Last modified date

    2016-06-03

  • 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

    WEB MESSAGE BRO

  • Fixed component ID

    5724J0520

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSKM8N","label":"WebSphere Message Broker"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
03 June 2016