IBM Support

PH40676: ALLOW WEBSPHERE APPLICATION SERVER TO RETURN JAR URLS RATHER THAN WSJAR

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • Some open-source frameworks throw errors when trying to process
    "wsjar:" URIs, and WebSphere Application Server does not provide
    a mechanism to return to "jar:" URIs
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of IBM WebSphere Application Server   *
    *                  whose applications are dependent on the     *
    *                  "jar"                                       *
    *                  protocol for resource URLs                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: WebSphere Application Server utilizes a *
    *                      custom URL protocol to manage jar files *
    *                      utilized by its class loaders           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The WebSphere Application Server class loaders use a custom URL
    protocol, "wsjar", to handle jar files, providing some
    additional
    internal functionality and lifecycle management. As a result,
    URLs
    returned by the class loader's getResource() method also use
    that
    protocol. This can cause issues for users whose applications are
    specifically dependent on the "jar" protocol being returned from
    a
    getResource() call.
    

Problem conclusion

  • The server can now be configured to utilize "jar" instead of
    "wsjar". To do this, add JVM custom property
    "com.ibm.ws.classloader.useJarUrls" with the value "true" or add
    "-Dcom.ibm.ws.classloader.useJarUrls=true" to the server's
    generic JVM arguments.
    
    The fix for this APAR is targeted for inclusion in fix packs
    8.5.5.22 and 9.0.5.11. For more information, see 'Recommended
    Updates for WebSphere Application Server':
    https://www.ibm.com/support/pages/node/715553
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH40676

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-09-16

  • Closed date

    2021-12-01

  • Last modified date

    2021-12-01

  • 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

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0"}]

Document Information

Modified date:
02 December 2021