PK91589: SIP PROXY FIXES NECESSARY FOR SIP FAILOVER

Fixes are available

APAR status

Closed as program error.

Error description

There are several session intiation protocol (SIP) Proxy
related fixes needed to finish up the SIP failover support on
Z/OS.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V7.0                                 *
****************************************************************
* PROBLEM DESCRIPTION: This is a cumulative APAR used for      *
*                      several Session Initiation Protocol     *
*                      (SIP) router/proxy issue when testing   *
*                      failover on Z/OS.                       *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
On every SIP message that flowed through the SIP router/proxy,
a call to java.net.InetHost.getLocalHost() was called.  This
is a very time consuming call that should only be called once.

When the custom property 'WLMStatefulSession' is set to true,
SIP requests should flow to all running Servant Regions.
There was a timing condition where this was not occurring.

When a failover occurs the SIP Router makes a CORBA call to
the Servant Region to start the recovery processing.   This
call can potentially take many seconds to complete.   These
CORBA calls were being made on a single thread which means
that we serialized the recovery processing.   This is not very
efficient and can cause some SIP calls to timeout.

If there are 3 or more app servers in a replication domain,
and an app server fails, the remaining application servers will
attempt to recover the calls for the failed app server.
Previously we ttempted to split this work between the
remaining application servers.   This meant that multiple
application servers were accessing the recovery log at the
same time which causes an abend to occur.

Problem conclusion

When the SIP router/proxy initializes itself, we cache the
value returned by the java.net.InetHost.getLocalHost() call
and use this value for each SIP message.

When the custom property 'WLMStatefulSession' is set to true,
we create temporary XMem connections (w/o affinity) to force
the Workload Manager (WLM) to activate all Servant Regions.

The CORBA calls are now made on seperate threads so that the
recovery of multiple LSNs can occur in parallel.

When an application server fails, the SIP router assigns the
recovery to only 1 of the remaining application servers.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.7.  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
PK91589
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
2009-07-16
Closed date
2009-09-22
Last modified date
2009-09-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

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"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:
24 October 2021

Tips

PK91589: SIP PROXY FIXES NECESSARY FOR SIP FAILOVER

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R700 PSY

Document Information

Share your feedback

Need support?