IBM Support

PM47143: CALL TO GETADDRESSHEADER FAILS WHEN THERE ARE MULTIPLE VALUES ON A CUSTOM HEADER.

Fixes are available

8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
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
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
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

  • If customer sends a multi-value diversion header:
    
    
    Diversion:  First <sip:+13103429200@72.11.192.10;user=phone>;
    privacy=off;reason=unconditional;counter=1,
    second<sip:+13103429100@72.
    11.192.10;user=phone>;privacy=off;reason=unconditional;counter=1
    
    Only the first diversion header is sent on the outgoing invite
    and diversion_params are changed to be part of the name_address:
    
    Diversion: "First"
    <sip:+13103429200@72.11.192.10;reason=unconditional;
    counter=1;privacy=off;user=phone>
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All Session Initiation Protocol (SIP)       *
    *                  container users of IBM WebSphere            *
    *                  Application Server                          *
    ****************************************************************
    * PROBLEM DESCRIPTION: Headers with multiple values are        *
    *                      parsed and serialized as line           *
    *                      seperated headers.                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The SIP container parse extended headers as line seperated
    headers by default even if the customer wanted to parse them
    as comma separated. The same issue exists in the outgoing side
    when the customer only has the ability to add line separated
    headers and not comma separated headers.
    

Problem conclusion

  • A new SIP container custom propery was added to control the
    header separation process.
    
    It affects the parsing of extension header fields, as well as
    the serialization of both standard and extension header fields.
    
    The default behavior is:
     1. Parse all extension header fields as if they are
    line-separated.
     2. Serialize all header fields as line separated, except
    for a specified set of header fields that are to be
    comma-separated.
    
    There is a configuration property that allows customizing
    separation. If set, it is processed on top of the default
    setting. Format:
    
    HeaderSeparation[,HeaderSeparation,...]
    HeaderSeparation = header[:separation]
    header = (either header name or *)
    separation = on/off/in/out (default is on)
    
    The default string is:
    
    "Accept,Accept-Encoding,Accept-Language,Allow,In-Reply-To,Proxy-
    Require,Require,Supported,Unsupported"
    
    During initialization, the custom string, if set, is
    appended on top of the default, before parsing the string.
    Duplicate entries are allowed, and the latter wins. If a
    header field name of "*" is specified, it erases all entries
    that come before it, and it specifies the default separation.
    
    For example, setting the custom property to
    "*:off,My-Header-Field:on" produces:
    "Accept,Accept-Encoding,Accept-Language,Allow,In-Reply-To,Proxy-
    Require,Require,Supported,Unsupported,*:off,My-Header-Field:on"
    which means all header fields are line-separated (including
    the default)
    except for My-Header-Field which is comma-separated.
    
    For setting the new SIP container custom property:
    1. log in to the Websphere Application Server administrative
    console
    2. go to Application servers > server1 > SIP container >
    Custom properties
    3. click on the new button
    4. set the following:
         name:comma.separated.headers
         value: as described above
    5. click on the OK button
    6. restart the SIP server
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 7.0.0.23 and 8.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

    PM47143

  • 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-09-06

  • Closed date

    2012-02-20

  • Last modified date

    2012-02-20

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    PM49196

Fix information

  • Fixed component name

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R700 PSY

       UP

  • R800 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM47143

Modified date: 20 February 2012