IBM Support

PM45309: SIP - SESSIONREADYTOINVALIDATE() IS NOT BEING CALLED

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • sessionReadyToInvalidate() is not being called when multiple
    applications are deployed.  When only one application is
    deployed, the call to the method occurs as expected.
    Session Initiation Protocol (SIP) container.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V8.0                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: 1. SIP Session listener methods are not *
    *                      called.                                 *
    *                      2. Possible memory leak when relaying   *
    *                      on                                      *
    *                      invalidateWhenReady feature.            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When Session Initiation Protocol (SIP) Session and SIP
    Application Session are not explicitly created by the
    application (that is, by calling getSession(true) methods),
    then the related listener methods will not be invoked by the
    container. Also, in the case that invalidateWhenReady feature
    is enabled, and this being the only invalidation method
    relayed upon by the application, there may be a memory leak
    from session related objects not getting cleared.
    

Problem conclusion

  • Memory leak problem was fixed by having the session/dialog
    related container internal objects cleared when sessions
    invalidated by raedyToInvalidate feature, even if actual
    session objects were not explicitly created. To enable this
    behaviour, the administrator needs to set up SIP container
    custom property:
    "enable.ready.to.invalidate.without.session" to the value of
    "true"
    
    Additionally there is a new option now to allow the application
    composer to get listener notifications even when session is not
    explicitly created by the application. Choosing this option
    will force the container to create the sessions on the
    reception or creation of the initial request, which will
    eliminate the performance benefits that come from the default
    no-demand session creation behaviour. If the composer prefers
    to have this mode of operation (usually it will be the case if
    the application was ported from another implementation of a SIP
    container where there are no on-demand sessions creation), then
    they should set the custom property:
    "create.sessions.when.listeners.exist" to the value of "true".
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.0.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

    PM45309

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-08-08

  • Closed date

    2011-09-16

  • Last modified date

    2011-09-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

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R800 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":"8.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
27 October 2021