PM01501: EJB INJECTION TARGET MISSING WHEN METADATACOMPLETEFORMODULES OPTION IS USED.

Fixes are available

APAR status

Closed as program error.

Error description

When an EJB is injected using the @EJB annotation and later the
module is marked metadata-complete using
MetadataCompleteForModules,
the EJB is not properly injected. The "injection-target" is
not being inserted into the deployment descriptor when WAS
writes the complete DD.

To Recreate:
1. Login to the Integrated Solutions Console.
2. Navigate to install a new enterprise application
(Applications >
Applications Types >
WebSphere enterprise applications > Install).
3. Select to install the "test.ear" application, and
continue through the installation wizard,
accepting all defaults.
4. Save the application.
5. Start the application.
6. Invoke the EJB from the servlet. The TestServlet
automatically invokes the EJB, for example, simply navigate to:
http://localhost:9080/xxx-web. (The EJB also writes some basic
debugging to System.out.)
* Note that the EJB is properly injected (the servlet
displays the xxxxService EJB and the time from the EJB)
7. Navigate to edit the application in the ISC, marking the web
module with metadata complete
* Navigate to Enterprise Applications > xxxxxx-test-app >
Metadata for modules
* Check the box for "metadata-complet attribute" next to
the "xxxxx-web" module
* Click OK, and SAVE.
8. Invoke the EJB from the servlet, by navigating to:
http://localhost:9080/xxx-web.
* Note that the EJB is null
If you inspect the web deployment descriptor, you'll notice that
the injection-target has not been inserted into the DD
for the TimeService ejb-local-ref, which is the cause of the
problem described in step 8.
==Alternatives==
* The same problem occurs if the xxxx-web module is marked with
metadata-complete during the initial installation
process.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server version 7.0.0.5 attempting           *
*                  injection using the @EJB annotation.        *
****************************************************************
* PROBLEM DESCRIPTION: The injections for targets identified   *
*                      by @EJB are not performed.              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The injection targets for @EJB were not included in the
merged deployment descriptor.

Problem conclusion

This APAR adds those injection targets identified using the
@EJB annotation to the merged view of the deployment descriptor.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.9.  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
PM01501
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
2009-11-17
Closed date
2009-12-10
Last modified date
2009-12-10

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":"BU053","label":"Cloud & Data Platform"},"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:
24 October 2021

Tips

PM01501: EJB INJECTION TARGET MISSING WHEN METADATACOMPLETEFORMODULES OPTION IS USED.

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?