IBM Support

PI81342: WEB SERVICE CALL IS FAILING AFTER APPLYING LATEST FIXPACKS + IFPI70810.

Fixes are available

9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Web service call is failing after applying latest fixpacks +
    IFPI70810.
    
    [8-5-17 15:08:52:451 CEST] 00000117 HttpOutboundC 1   Exception
    caught
    in oConn.connect attempt:java.lang.NumberFormatException: null
     at java.lang.Integer.parseInt(Integer.java:466)
     at java.lang.Integer.parseInt(Integer.java:539)
     at
    com.ibm.ws.ssl.channel.impl.SSLConnectionLink.connect(SSLConnect
    ionLink.
    java:1063)
     at
    com.ibm.wsspi.channel.base.OutboundProtocolLink.connect(Outbound
    Protocol
    Link.java:87)
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server Version    *
    *                  8.5.5 and 9.0 Traditional Profile users of  *
    *                  the SSL Channel                             *
    ****************************************************************
    * PROBLEM DESCRIPTION: The SSL Channel may throw a             *
    *                      java.lang.NumberFormatException when    *
    *                      using useProxyEndpointInformation       *
    *                      without defining a proxy                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    If the SSL Channel custom property
    "useProxyEndpointInformation"
    is enabled, but the channel is not provided any proxy endpoint
    connection information, the channel may throw a number format
    exception such as:
    [8-5-17 15:08:52:451 CEST] 00000117 HttpOutboundC 1 Exception
    caught in oConn.connect attempt:java.lang.Number
    FormatException: null
    at java.lang.Integer.parseInt(Integer.java:466)
    com.ibm.ws.ssl.channel.impl.SSLConnectionLink.connect
    (SSLConnectionLink.java:1063)
    

Problem conclusion

  • The SSL Channel was modified to account for configurations
    where the property is enabled but no proxy is defined. In this
    case, if no proxy hostname is provided, the proxy's peer
    connection information is utilized. This is functionally
    equivalent to the custom property being disabled. If a proxy
    hostname is provided, but the port is not, the proxy hostname
    is updated and the port will be defaulted to port 80.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.5.13 and 9.0.0.5.  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

    PI81342

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-05-09

  • Closed date

    2017-07-19

  • Last modified date

    2017-09-26

  • 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

  • R850 PSY

       UP

  • R900 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:
07 December 2021