IBM Support

PI51393: ISSUES WITH MIXED IPV4/IPV6 SIP SUPPORT

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The OPTIONS request is created by the servlet and then
    is processed by the servlet again twice (that is, 2 invocations
    of the servlet for the message).  The servlet is calling
    setOutboundInterface() for this request (after the initial
    createRequest() call and also during each invocation of the
    servlet for the request).
    
    
    [10/19/15 22:02:15:097 IST] 0000007e SipConnLink   3
    SipConnLink connectionError error
    
    java.net.SocketTimeoutException: Socket operation timed out
    before it could be completed
    at
    com.ibm.ws.tcp.channel.impl.ConnectChannelSelector.checkForTimeo
    uts(ConnectChannelSelector.java:291)
    at
    com.ibm.ws.tcp.channel.impl.ChannelSelector.run(ChannelSelector.
    java:245)
    at java.lang.Thread.run(Thread.java:795)
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V8.5 Session Initiation Protocol     *
    *                  (SIP)                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION: Outgoing connection created from the    *
    *                      incorrect Listening Point in            *
    *                      SipContainer                            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    An outgoing connection is created from the incorrect Listening
    Point in the SipContainer in the case when an application
    decides to use the Outbound Interface List defined for JSR 289
    applications
    

Problem conclusion

  • Fixed the outgoing connection creation process. Now the
    connection is created from the outbound interface selected by
    the application and not from the Listening Point.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.5.10.  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

    PI51393

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-10-28

  • Closed date

    2016-01-14

  • Last modified date

    2016-06-09

  • 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

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

Document Information

Modified date:
28 April 2022