PM79829: APPLICATION SERVER MUST TOLERATE BOTH IBM-MANAGED-BEAN-BND.XML AND IBM-MANAGED-BEANS-BND.XML METADATA

8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15

APAR status

• Closed as program error.

Error description

• Following exception is seeing when using Resource injection in
  Managed bean
  
  ***********
  public class ConnectionManager
  
  {
  @Resource(name="jdbc/supplierDB",
  authenticationType=AuthenticationType.CONTAINER,
  type=DataSource.class,
  shareable=true) DataSource suppDB;
  @Resource(name="jdbc/busPartDB",
  authenticationType=AuthenticationType.CONTAINER,
  type=DataSource.class,
  shareable=true) DataSource busPartDB;
  
  @Produces @Supplier @RequestScoped
  public Connection getSupplierConnection()
  {
  System.out.println("Producer method called");
  try{
  return suppDB.getConnection();
  }catch(SQLException e){
  throw new RuntimeException(e);
  }
  }
  
  The rational software architect tooling generates a managed bean
  bindings file (ibm-managed-bean-bnd.xml) into which following
  input entries are created in bindings for resources
  
  <managed-bean-bnd xmlns="http://websphere.ibm.com/xml/ns/javaee"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://websphere.ibm.com/xml/ns/javaee
  http:
  //websphere.ibm.com/xml/ns/javaee/ibm-managed-bean-bnd_1_0.xsd"
  version="1.0">
  <managed-bean
  class="com.ibm.issw.taxonomy.producers.ConnectionManager"
  >
  <resource-ref name="jdbc/supplierDB" binding-name="jdbc/ptiDS"
  />
  <resource-ref name="jdbc/busPartDB" binding-name="jdbc/ptiDS"
  />
  </managed-bean>
  </managed-bean-bnd>
  
  **********
  
  This causes the following exceptions
  
  [11/26/12 8:05:23:159 EST] 00000023 InjectionBind E
  CWNEN0030E: The
  com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory@26067033
  factory
  encountered a problem getting the object instance Reference
  Class Name:
  java.lang.Object
  Type: JndiLookupInfo
  Content:
  com.ibm.ws.naming.util.JndiLookupInfo@45f3e8e1[_jndiName="java:
  comp/env/jdbc/supplierDB", _providerURL="",
  _initialContextFactory=""]
  binding object.
  [11/26/12 8:05:23:168 EST] 00000023 FfdcProvider  W
  com.ibm.ws.ffdc.
  impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted
  on
  /opt/ibm/WebSphere/AppServer/profiles/wxsProf01/logs/ffdc/server
  1_fd82ba
  a3_12.11.26_08.05.23.1628844616
  102198903158.txt
  com.ibm.wsspi.injectionengine.InjectionTarget.inject 97
  [11/26/12 8:05:23:169 EST] 00000023 InjectionTarg E
  CWNEN0028E: The
  injection engine encountered an error injecting jdbc/supplierDB
  into
  javax.sql.DataSource
  com.ibm.issw.taxonomy.producers.ConnectionManager.
  suppDB
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server using managed beans bindings.        *
  ****************************************************************
  * PROBLEM DESCRIPTION: Applications with managed beans         *
  *                      bindings may have compatibility issues  *
  *                      with IBM stack products.                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Deploying Java EE6 specification applications with Managed
  Beans in either EJB or WEB modules may have issues with stack
  product compatibility.
  The addition of Managed Beans bindings, for example through
  Managed Bean EJB references, resource references, or
  environment entries, creates Managed Beans binding files.
  These were being saved in ibm-managed-beans-bnd.xml files in
  those deployed modules, with an XML tag of <managed-beans-bnd>.
  The shipped schema for these bindings instead describes a
  ibm-managed-bean-bnd.xml file, with a <managed-bean-bnd>
  element (note "bean" is singular). These schema correct
  versions are what current WebSphere Application Server stack
  products, including Rational Application Developer, use to
  link with the Application Server.
  

Problem conclusion

• The Application server must tolerate and read both files to be
  both schema correct, and backwards compatible with earlier
  versions of the Application Server.
  
  Modules deployed with only "ibm-managed-beans-bnd.xml" files
  will read that data and save the deployed module with only an
  "ibm-managed-bean-bnd.xml" file.
  
  Modules deployed with both "ibm-managed-beans-bnd.xml" and
  "ibm-managed-bean-bnd.xml" files will read the schema correct
  "ibm-managed-bean-bnd.xml" file and save the deployed module
  with only an "ibm-managed-bean-bnd.xml" file.
  
  Modules deployed with only a "ibm-managed-bean-bnd.xml" file
  will read that file and save back to the same file in the
  deployed module.
  
  Exporting a deployed module, for example to open in Rational
  Application Developer, will also always export to the schema
  correct version.
  
  The fix for this APAR is currently targeted for inclusion in
  fix packs 8.0.0.7 and 8.5.5.  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 is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels

• R800 PSY

     UP

• R850 PSY

     UP