IBM Support

PI38330: LIBRARY.POLICY IS NOT APPLIED TO NON-ISOLATED SHARED LIBRARY BUT IS APPLIED TO ISOLATED SHARED LIBRARY MAY SEE SECJ0314W

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • When trying to configure Java 2 security policy files you will
    see an issue if you are using non-isolated shared libraries and
    want to put your Java 2 security permissions in the
    library.policy file.  The permissions will not be applied.
    The usual result is SECJ0314W complaining about the permission
    that you expected to be applied not being granted.
    

Local fix

  • use was.policy,  or package code in war and use app.policy, or
    use an isolated shared library and use library.policy
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: library.policy permissions are not      *
    *                      applied to non-isolated shared          *
    *                      libraries associated with web modules   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When WebSphere Application Server application and module class
    loaders are created, security policy settings are configured
    on those loaders' code sources based on the appropriate
    security policy.  However, the configuration specified in
    library.policy was not applied to paths of non-isolated shared
    libraries associated with a web module's class loader.  Shared
    libraries using an isolated class loader did not see this
    issue, as they were given their own separate class loader.
    

Problem conclusion

  • Additional processing was added to ensure that shared library
    paths were associated with the appropriate security
    policy.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 7.0.0.39, 8.0.0.12, and 8.5.5.8.  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

    PI38330

  • 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

    2015-04-02

  • Closed date

    2015-06-29

  • Last modified date

    2015-06-29

  • 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

  • R700 PSY

       UP

  • R800 PSY

       UP

  • R850 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 850

Reference #: PI38330

Modified date: 29 June 2015