IBM Support

PM41522: IMPROVE CLIENT JMX NOTIFICATION PERFORMANCE

Fixes are available

7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Requirement is to reduce wait time to deploy a BLA application
    when using the SOAP/IPC connector to be equal to the time it
    takes when using a RMI connector.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application Server
    ****************************************************************
    * PROBLEM DESCRIPTION: The amount of time it takes to deploy   *
    *                      a BLA Application using SOAP/IPC        *
    *                      connectors is significant more          *
    *                      than the time it takes  to deploy a     *
    *                      BLA Application when using RMI          *
    *                      connector.                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The amount of time it takes to deploy
    a BLA Application using SOAP/IPC
    connectors is significant more
    than the time it takes  to deploy a
    BLA Application when using RMI
    connector.
    

Problem conclusion

  • The amount of time it takes to deploy a BLA Application
    using SOAP/IPC connectors will be reduced to be the same or
    very close to the time it takes  to deploy a BLA Application
    when using RMI connector.
    1. Client Side:
    A new  system property can be set on the  client
    com.ibm.ws.management.event.max_polling_interval  to take
    advantage of this function. The default  value is 20000  ms
    (20 secs)
    You can set this property in your wsadmin.bat script.   Value
    must be between 0 and 20000 ms , otherwise the default value
    will be used.
    
    2. Server Side:
    A new  system property can be set on the  dmgr
    com.ibm.ws.management.event.pull_notification_timeout  to take
    advantage of this function.  Default value is 60000 (1 min)
    Value can be any number in milliseconds  greater than 0
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.19  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

    PM41522

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-06-14

  • Closed date

    2011-06-16

  • Last modified date

    2011-06-16

  • 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

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
27 October 2021