IBM Support

PM26784: Lock contention may occur with a JAX-RPC application when the BeanSerializerFactory uses FilePermissionCollection.

Fixes are available

6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Multiple threads may lock on the FilePermission code when
    running a JAX-RPC application.  These locks may reduce overall
    system throughput.
    
    Here is an example stack that may be seen within a javacore
    file:
    
    java/io/FilePermissionCollection.implies
    
    org/eclipse/osgi/framework/internal/core/ConditionalPermissionSe
    t.implies
    
    org/eclipse/osgi/framework/internal/core/BundleCombinedPermissio
    ns.implies
    
    java/security/ProtectionDomain.implies
    
    java/security/AccessController.checkPermission
    
    java/lang/SecurityManager.checkPermission
    
    com/ibm/ws/security/core/SecurityManager.checkPermission
    
    java/lang/SecurityManager.checkMemberAccess
    
    java/lang/Class.checkMemberAccess
    
    java/lang/Class.getDeclaredMethods
    
    com/ibm/ws/webservices/engine/utils/JavaUtils._getValueMethod
    
    com/ibm/ws/webservices/engine/utils/JavaUtils.isEnumClass
    
    com/ibm/ws/webservices/engine/encoding/ser/BeanSerializerFactory
    .<init>
    com/ibm/ws/webservices/engine/encoding/ser/BeanSerializerFactory
    .create
    sun/reflect/GeneratedMethodAccessor62.invoke
    
    sun/reflect/DelegatingMethodAccessorImpl.invoke
    
    java/lang/reflect/Method.invoke
    
    com/ibm/ws/webservices/engine/encoding/ser/BaseSerializerFactory
    $CreateFactoryPRIV.run
    
    java/security/AccessController.doPrivileged
    
    com/ibm/ws/security/util/AccessController.doPrivileged
    
    com/ibm/ws/webservices/engine/encoding/ser/BaseSerializerFactory
    .createFactory
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server V6.1 and   *
    *                  V7.0 users or administrators of JAX-RPC     *
    *                  applications                                *
    ****************************************************************
    * PROBLEM DESCRIPTION: Lock contention may occur with a        *
    *                      JAX-RPC application when the            *
    *                      BeanSerializerFactory uses              *
    *                      FilePermissionCollection.               *
    ****************************************************************
    * RECOMMENDATION:  Install a fix pack containing this APAR.    *
    ****************************************************************
    Multiple threads may lock on the FilePermission code when
    running a JAX-RPC application.  These locks may reduce overall
    system throughput.
    
    Here is an example stack that may be seen within a javacore
    file:
    
    java/io/FilePermissionCollection.implies
    
    org/eclipse/osgi/framework/internal/core/ConditionalPermissionSe
    t.implies
    
    org/eclipse/osgi/framework/internal/core/BundleCombinedPermissio
    ns.implies
    
    java/security/ProtectionDomain.implies
    
    java/security/AccessController.checkPermission
    
    java/lang/SecurityManager.checkPermission
    
    com/ibm/ws/security/core/SecurityManager.checkPermission
    
    java/lang/SecurityManager.checkMemberAccess
    
    java/lang/Class.checkMemberAccess
    
    java/lang/Class.getDeclaredMethods
    
    com/ibm/ws/webservices/engine/utils/JavaUtils._getValueMethod
    
    com/ibm/ws/webservices/engine/utils/JavaUtils.isEnumClass
    
    com/ibm/ws/webservices/engine/encoding/ser/BeanSerializerFactory
    .<init>
    com/ibm/ws/webservices/engine/encoding/ser/BeanSerializerFactory
    .create
    sun/reflect/GeneratedMethodAccessor62.invoke
    
    sun/reflect/DelegatingMethodAccessorImpl.invoke
    
    java/lang/reflect/Method.invoke
    
    com/ibm/ws/webservices/engine/encoding/ser/BaseSerializerFactory
    $CreateFactoryPRIV.run
    
    java/security/AccessController.doPrivileged
    
    com/ibm/ws/security/util/AccessController.doPrivileged
    
    com/ibm/ws/webservices/engine/encoding/ser/BaseSerializerFactory
    .createFactory
    

Problem conclusion

  • The JAX-RPC runtime inspects each XML serializer and
    deserializer to determine if the XML construct represents an
    enumeration.  This detection code causes excessive locking
    while obtaining permission to inspect the class.  The
    detection code is moved from the initialization logic to a
    later point in the code.  This deferral should eliminate most
    of the detection calls.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 6.1.0.37 and 7.0.0.17.  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

    PM26784

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-11-15

  • Closed date

    2010-11-22

  • Last modified date

    2010-11-22

  • 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

  • R700 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM26784

Modified date: 22 November 2010