PM75837: OPTIMIZE TOPIC SECURITY CHECKS DURING MESSAGE PROCESSING

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Optimize Topic security checks during message processing. Messag
    processing for publishing and subscribing messages when bus
    security is on is taking a lot of time. This is because each and
    every time, when a message is being published or subscribed, we
    are checking the authorization for the User.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: When bus security is enabled and the    *
    *                      messages are published or subscribed    *
    *                      from a topicspace, before each          *
    *                      message gets processed, security        *
    *                      check happens to check if the user is   *
    *                      valid or not. This is impacting the     *
    *                      rate at which the message is            *
    *                      published or subscribed from the        *
    *                      topicspace when bus security is         *
    *                      enabled.                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Stack products need the ability to cache the users such that
    SIBus will not verify the user authentication and authority
    before each publish or subscribe call for the same user. The
    security checks will happen again once a user is removed from
    the cache after a timeout has occured. The caching mechanism
    is controlled by a custom property set at the bus level. The
    custom property "sib.security.userCacheTimeout" defines the
    timeout value of the cache and also is responsible for
    enabling or disabling the feature. This custom property can
    vary between 1 to 100 seconds. The main reason for introducing
    the caching feature is to improve the performance for the
    rate at which messages gets published or subscribed when
    security is enabled.
    

Problem conclusion

  • A caching mechanism is introduced in SIBus to avoid the number
    of security checks happening at the time of publish or
    subscribe to improve the overall performance.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.5.0.2.  Please refer to the Recommended Updates
    page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM75837

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-10-25

  • Closed date

    2013-03-22

  • Last modified date

    2013-03-22

  • 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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R700 PSY

       UP

  • R800 PSY

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

WebSphere Application Server
General

Software version:

850

Reference #:

PM75837

Modified date:

2013-03-22

Translate my page

Machine Translation

Content navigation