PM06749: IF A SIP PROXY IS IN A STARTUP DELAY, THE SIP CONTAINER MAY SEND MESSAGES TO IT BEFORE IT IS READY.

Fixes are available

APAR status

Closed as program error.

Error description

When a Session Initiation Protocol (SIP) Proxy starts it may be
configured with a startup delay. During this delay, it will
not accept messages from a client. Currently, the SIP
Container doesn't know about this delay and could possibly
send a SIP request to a client (via a proxy). The transmission
of the request would succeed, but the response from the client
would be dropped by the proxy. This is a startup
synchronization issue.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server using Session Initiation Protocol    *
*                  (SIP) Proxy                                 *
****************************************************************
* PROBLEM DESCRIPTION: When a SIP proxy is started up and is   *
*                      in a "startup delay", the SIP           *
*                      containers should NOT send any data     *
*                      to this proxy.                          *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When the SIP containers send data to a SIP proxy when its in a
"startup delay", the SIP proxy is possibly unable to route
packets effectivly back into the cluster.  The SIP container
needs to ensure that the "startup delay" is completed on the
SIP proxy before sending any data through it.

Problem conclusion

The SIP Proxy no longer informs the SIP container of its
presence until after the "startup delay" is completed.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.11.  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
PM06749
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
2010-02-03
Closed date
2010-03-10
Last modified date
2010-03-10

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:
25 October 2021

Tips

PM06749: IF A SIP PROXY IS IN A STARTUP DELAY, THE SIP CONTAINER MAY SEND MESSAGES TO IT BEFORE IT IS READY.

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?