Fixes are available
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
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
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
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
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
Obtain the fix for this APAR.
APAR status
Closed as program error.
Error description
After redeploying a WebSphere XD batch application with either a new resource reference for a non-XA datasource or a new batch step, the user sees naming exceptions because the new references could not be found. After restarting the application server we no longer see the exception. ---------------------------------------------------------------- i.e.: With the new app, a new resource reference is introduced: (java:comp/env/jdbc/WXD_T2), but here's what is seen in the NameSpaceDump: 14 (top)/comp/env/jdbc/WXD_T2 14 ERROR: Could not instantiate a bound object. 14 Bound Java type: java.lang.Object 14 Local Java type: NULL 14 String representation: 14 Source object is a javax.naming.Reference. 14 Reference factory class name: com.ibm.ws.util.ResRefJndiLookupObjectFactory 14 RefAddr[0]: Type: ResRefJndiLookupInfo Content: com.ibm.ws.util.ResRefJndiLookupInfo@1e681e68 ResRefJndiLookupInfo: Look up Name="jdbc/WXD_T2";JndiLookupInfo: jndiName="jdbc/WXD_T2"; providerURL=""; initialContextFactory="" ---------------------------------------------------------------- Steps to reproduce the issue: 1. Install WXD_IVTPlain (sr-wxd-ivt3-ear-1.0.ear) in your UTE. On purpose this application version is missing some resource references that will cause a NamingException. 2. Restart the application server. 3. Run the EJBErrorTest_CrusorHoldable.xml via Job Management Console 4. Stop the enterprise application WXD_IVTPlain 5. Deinstall the enterprise application WXD_IVTPlain 6. Install the new Version of WXD_IVTPlain ( sr-wxd-ivt3-ear-1.1.ear) that will have the missing resource references *** DO NOT RESTART THE APPLICATION SERVER *** 7. Run the EJBErrorTest_CrusorHoldable.xml via Job Management Console 8. The new introduced resource references should be accessibl via local JNDI Namespace (java:comp/env/jdbc/WXD_T2). The resource reference is added to the BatchControllerBean but the running enterprise application does not find it. In this example the error happened in the BatchDataStream->open() where the existing resource reference is not found even it's there: System.out: [09/30/09 18:02:07:650 CEST] ERROR JDBCBatchDataStreamReader - open: Caught NamingException: javax.naming.NameNotFoundException: Name comp/env/jdbc not found in context "java:". 9. Now restart the application server 10. Run the EJBErrorTest_CrusorHoldable.xml via Job Management Console *** Now the problem is gone *** e
Local fix
Only workaround is to restart the application server
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V6.1.0 who update an application * * with another module of new resource * * reference * **************************************************************** * PROBLEM DESCRIPTION: Lookup of resource fails when the * * resource had been added during the * * application update * **************************************************************** * RECOMMENDATION: * **************************************************************** Steps to reproduce the problem ----------------------------------- 1)Install Application with two EJBs EJB1 and EJB2 2)EJB1 does a lookup on EJB2 which works fine 3)Update the application to have one more EJB, EJB3 and modify EJB1 to do a lookup on both EJB2 and EJB3 A NameNotFound exception is thrown. Only a restart of the server could make the lookup of the other resource work.
Problem conclusion
The component metadata cache which is used to map the name with component metadata was not updated with other resources when the application is updated. Code has been modified to accomodate the same. APAR PM17412 is currently targeted for inclusion in Service Level (Fix Pack) 6.1.0.35 of WebSphere Application Server V6.1. Please refer to URL: //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970 for Fix Pack availability.
Temporary fix
Comments
APAR Information
APAR number
PM17412
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
610
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-06-28
Closed date
2010-09-14
Last modified date
2011-01-24
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 FOR Z
Fixed component ID
5655I3500
Applicable component levels
R610 PSY UK62676
UP10/12/17 P F012
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
Document Information
Modified date:
25 October 2021