Fixes are available
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.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.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
Customer gets missing resource references when two EJBs extend the same base class during the deployment of the application. In WebSphere Application Server 7.0.0.25 (and earlier versions), the failure is that the administrative console only offers the option to bind a data source reference for the first EJB. The merged deployment descriptor also only contains a resource-ref for the first EJB. At runtime, the first EJB works fine, but the second fails because the resource reference isn't bound.
Local fix
na
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V7.0 using the @Resource annotation * **************************************************************** * PROBLEM DESCRIPTION: An @Resource annotation defined on a * * field or method of a superclass, * * sometimes will not be applied to all * * EJBs that extend the superclass * **************************************************************** * RECOMMENDATION: * **************************************************************** The processing of an @Resource annotation which is defined in a superclass fails to identify all of the EJB classes which extend the superclass. As a result, the annotation is not inherited by some EJBs and is not included in the definition of the EJB in the deployment descriptor.
Problem conclusion
The annotation processing has been corrected to identify all EJBs which extend a class containing a @Resource annotation. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.29. 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
PM76181
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-10-31
Closed date
2013-01-25
Last modified date
2013-05-14
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
R700 PSY
UP
Document Information
Modified date:
29 October 2021