IBM Support

PM75926: ALLOW EJB 3.0 JNDIS AND JNDI NAMES FOR EJB REFERENCES TO BE SET THROUGH A CUSTOM DEFAULT BINDINGS STRATEGY FILE

Fixes are available

8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
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

  • When a custom default bindings strategy file is used during
    application deployment, allows EJB 3.0 JNDIs and JNDIs for ejb
    reference from an EE5 module to be set.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server.                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: Any JNDI values specified in the        *
    *                      default bindings custom strategy file   *
    *                      for EJB 3.x beans and EJB 3.x           *
    *                      references are not honored during       *
    *                      application deployment.                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Any JNDI values specified in the default bindings custom
    strategy file for EJB 3.x beans and EJB 3.x references are not
    honored during application deployment.
    

Problem conclusion

  • The code has been modified to allow you to set the custom
    property
    com.ibm.websphere.management.application.client.customStrategy.a
    llowEJB3xDefaultBindings on the JVM to true/false to override
    the default settings.
    
    1) To enable the System Property in the Administrative Console:
    
    a) In a Network Deployment environment, the system property
    needs to be set on the DMGR. System administration -->
    Deployment manager --> Java and Process Management --> Process
    Definition --> Java Virtual Machine --> Custom Properties
    Name:
    com.ibm.websphere.management.application.client.customStrategy.a
    llowEJB3xDefaultBindings Value : true/false
    
    b) In a Base environment, the system property is set on
    server1. Servers --> Application Servers --> server1 --> Java
    and Process Management --> Process Definition --> Java Virtual
    Machine --> Custom Properties Name :
    com.ibm.websphere.management.application.client.customStrategy.a
    llowEJB3xDefaultBindings Value : true/false
    
    2) To enable the System Property in wsadmin it must be set as
    an option when starting wsadmin or in the wsadmin.properties
    file.
    
    a) To set the System Property when starting wsadmin do the
    following: wsadmin -javaoption
    "-Dcom.ibm.websphere.management.application.client.customStrateg
    y.allowEJB3xDefaultBindings="
    
    b) To set the System Property in the wsadmin.properties file,
    found at /profiles//properties, add the following line (value
    can be false or true):
    com.ibm.websphere.management.application.client.customStrategy.a
    llowEJB3xDefaultBindings=false
    
    The fix for this APAR is currently targeted for inclusion in
    fixpacks 7.0.0.29, 8.0.0.6 and 8.5.0.2.  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

    PM75926

  • 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

    2012-10-26

  • Closed date

    2012-12-13

  • Last modified date

    2012-12-13

  • 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: 7.0

Reference #: PM75926

Modified date: 13 December 2012