Fixes are available
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
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
APAR status
Closed as program error.
Error description
Products: WebSphere Application Server Network Deployment edition 7.0.0.11 WebSphere Application Server Base 7.0.0.5 Operating System: Red Hat Linux v2.5 Microsoft Windows XP ... Problem Description: An EAR contains a single ejb-jar (zztest2) that contains two Message Driven Beans (MDB1 and MDB2). Each of the MDBs contains a resource reference to a data source. MDB1 contains a resource reference called jdbc/one and MDB2 contains a resource reference called jdbc/two. When a user runs the following command in wsadmin: AdminApp.install('C:/atd/soi4/zztest2ear.ear', ['-appname', 'ZZTEST2', '-server', 'server1']) the user then gets the following error: ----------------------------------------------------------- WASX7090I: Executing command: "AdminApp.install('C:/atd/soi4/zztest2ear.ear', ['-appname', 'ZZTEST2', '-server', 'server1'])" [14/10/10 10:08:56:161 BST] 00000000 AbstractShell E WASX7120E: Diagnostic information from exception with text "com.ibm.ws.scripting.ScriptingException: WASX7109E: Insufficient data for install task "MapResRefToEJB ADMA0007E: A Validation error occurred in task Mapping resource references to resources. The Java Naming and Directory Interface (JNDI) name is not specified for reference binding jdbc/two in module zztest2 with EJB name MDB1. ADMA0007E: A Validation error occurred in task Mapping resource references to resources. The Java Naming and Directory Interface (JNDI) name is not specified for reference binding jdbc/one in module zztest2 with EJB name MDB2." " follows: com.ibm.ws.scripting.ScriptingException: WASX7109E: Insufficient data for install task "MapResRefToEJB ADMA0007E: A Validation error occurred in task Mapping resource references to resources. The Java Naming and Directory Interface (JNDI) name is not specified for reference binding jdbc/two in module zztest2 with EJB name MDB1. ADMA0007E: A Validation error occurred in task Mapping resource references to resources. The Java Naming and Directory Interface (JNDI) name is not specified for reference binding jdbc/one in module zztest2 with EJB name MDB2." at com.ibm.ws.scripting.AbstractShell.setAndThrowScriptingException (AbstractShell.java:1837) at com.ibm.ws.scripting.AdminAppClient.prepare(AdminAppClient.java: 3118) at com.ibm.ws.scripting.AdminAppClient.commonPrepare(AdminAppClient .java:3031) ... ... ---------------------------------------------------------------- It looks like AdminApp.install is incorrectly looking for a jdbc/two binding in MDB1 and a jdbc/one binding in MDB2. This is incorrect as jdbc/one is only defined in MDB1 and jdbc/two is only defined in MDB2. The AdminApp.install only works if both MDBs contain exactly the same resource reference definitions. When the MapResRefToEJB task data was populated, duplicate resource reference data were populated. For each EJB, the resource reference of other EJB was also returned and made incorrect mapping, hence validation logic throws the error for the incorrect duplicate task data.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server deploying Enterprise Java Beans * * (EJBs) * **************************************************************** * PROBLEM DESCRIPTION: An EJB resource reference associated * * with an EJB which has the same EJB * * class name as another EJB will * * incorrectly be placed on both EJBs. * **************************************************************** * RECOMMENDATION: * **************************************************************** The processing of Enterprise Java Bean (EJB) resource references, which occur in EJB deployment descriptors (ejb-jar.xml), will incorrectly duplicate the resource references when the associated EJBs use the same EJB class name. The problem manifests as a validation error, for example: com.ibm.ws.scripting.ScriptingException: WASX7109E: Insufficient data for install task "MapResRefToEJB" ADMA0007E: A Validation error occurred in task Mapping resource references to resources. The Java Naming and Directory Interface (JNDI) name is not specified for reference binding jdbc/two in module test_module with EJB name EJB_1. ADMA0007E: A Validation error occurred in task Mapping resource references to resources. The Java Naming and Directory Interface (JNDI) name is not specified for reference binding jdbc/one in module test_Module with EJB name EJB_2."
Problem conclusion
Code was updated to correctly process the resource references. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.23. 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
PM34614
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
2011-03-11
Closed date
2012-02-02
Last modified date
2012-02-02
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
Document Information
Modified date:
27 October 2021