PK74708: AFTER FAILED SEND TO FIRST NETWORK ELEMENT, PROXY RESENDS TO FIRST NETWORK ELEMENT

Fixes are available

APAR status

Closed as program error.

Error description

If we send to the first Network Element (NE) and it fails
(expected in test case), and then we send to the second
Network Element, even though the Session Initiation Protocol
(SIP) message shows the second NE, the proxy sends to the
first NE again.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of WebSphere Application Server   *
*                  V6.1 and V7.0                               *
****************************************************************
* PROBLEM DESCRIPTION: Request created from original request   *
*                      shows the correct destination but the   *
*                      proxy sends it to the original          *
*                      destination.                            *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The problem was that when using the
createRequest(Request,boolean) interface to create a message
to the next destiation (using the original mesage), the
IBM-Destination header was copied with a bunch of other
headers. This header tells the proxy where to send the message.
This means that even if the new message details are correct,
the proxy will only take the IBM-Destination into consideration
and ignore the rest.

Problem conclusion

The fix made was that when using the
createRequest(Request,boolean) interface to create a message
from another message the IBM-Destination header will not be
copied. This will subsequently cause the destination to be
recalculated from the new Request.


The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.23 and 7.0.0.3.  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
PK74708
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61I
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-10-29
Closed date
2008-12-08
Last modified date
2008-12-08

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

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z 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":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PK74708: AFTER FAILED SEND TO FIRST NETWORK ELEMENT, PROXY RESENDS TO FIRST NETWORK ELEMENT

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

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

Document Information

Share your feedback

Need support?