IBM Support

PK68016: URLConnection.getInputStream for the wsjar returns null rather than throwing a FileNotException.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The URLConnection.getInputStream for the wsjar protocol
    erroneously returns null rather than throwing a
    FileNotFoundException like the builtin jar protocol.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server V6.1 Users *
    *                  of URLConnection.getInputStream.            *
    ****************************************************************
    * PROBLEM DESCRIPTION: The wsjar protocol handler returns      *
    *                      null from URLConnection.getInputStream  *
    *                      when a zip file entry is not found      *
    *                      rather than throwing a                  *
    *                      FileNotFoundException like the jar      *
    *                      protocol handler.                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When a class loader locates a resource in a zip file, it
    returns a URL with a wsjar protocol handler.  If that URL is
    used as the context for constructing a new URL for an entry
    that does not exist, URLConnection.getInputStream will return
    null rather than throwing a FileNotFoundException like the jar
    protocol handler.
    

Problem conclusion

  • The wsjar protocol handler is changed to throw
    FileNotFoundException from URLConnection.getInputStream when
    the JVM custom property
    com.ibm.ws.classloader.getInputStream.enableIOException is set
    to true.  If the property is unset or set to false, then the
    current behavior of returning null is retained.
    The fix for this APAR is currently targeted for inclusion in
    fix pack 6.1.0.21.  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

    PK68016

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    61A

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-06-23

  • Closed date

    2008-06-26

  • Last modified date

    2008-06-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

  • 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