Fixes are available
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
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.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
APAR status
Closed as program error.
Error description
Two EJB applications are deployed onto WebSphere Application Server v7.0.0.17. In EAR1 there is one Stateless EJB with a Remote Interface and no Bindings File (AutoLink Feature of WebSphere Application Server is used) In EAR2 there is another Stateless EJB which references the first one using @EJB (Dependency Injection) and an EJB Bindings file. If the code of the second EJB contains also the injection: @Resource private EJBContext context; then the following warning appears in the SystemOut.log when the second EAR is deployed: [22-7-11 17:44:17:215 CEST] 0000000b serialization W EjbRefBindingImpl(anon) eResolveProxy No matching ref for name [ Bean1Remote ] If that injection of the EJBContext is absent, then the warning does not appear.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V7.0 deploying J2EE version 5 * * applications with an EJB that contains * * both @Resource and @EJB annotations * **************************************************************** * PROBLEM DESCRIPTION: When a deployed application contains * * both @Resource and @EJB annotations, * * an error message can occur during * * application start. * **************************************************************** * RECOMMENDATION: * **************************************************************** During application installation, an entry is created in the bindings file for the EJB reference denoted by the @EJB annotation. While starting the application, the @Resource annotaion is processed before the @EJB annotation. This processing requires that the bindings file be loaded. During the loading of the bindings file, the EJB references in it are resolved by finding the matching EJBs. Since the @EJB annotations have not yet been processed, there is no matching EJB reference found and the following warning message is displayed. 22-7-11 17:44:17:215 CEST] 0000000b serialization W EjbRefBindingImpl(anon) eResolveProxy No matching ref for name [ Bean Name ]
Problem conclusion
No workaround exists. Annotation processing has been changed so that the @EJB annotations are processed before the @Resource annotations. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.21. 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
PM47575
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-09-12
Closed date
2011-09-29
Last modified date
2011-09-29
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:
28 October 2021