PM47575: "NO MATCHING REF FOR NAME" SERIALIZATION ERROR THROWN WHEN USING @RESOURCE ANNOTATION

Fixes are available

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

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 October 2021

Tips

PM47575: "NO MATCHING REF FOR NAME" SERIALIZATION ERROR THROWN WHEN USING @RESOURCE ANNOTATION

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R700 PSY

Document Information

Share your feedback

Need support?