PK97815: DO NOT PUT SERVLET IN SERVICE AFTER INJECTION FAILURE.

Fixes are available

APAR status

Closed as program error.

Error description

Resources or EJB injection failures are reported in the logs but
are not propagated to the client and servlet is allowed to
initialize and go in service. This may result in a
NullPointerException if the failed injected object is
referenced.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V7.0                                 *
****************************************************************
* PROBLEM DESCRIPTION: An injection failure during             *
*                      initialization of a servlet is not      *
*                      propagated to the client and does not   *
*                      result in the servlet being taken out   *
*                      of service.                             *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
If a resource or EJB injection fails during servlet
initialization, an error message is written to the server
logs, but an error is not propagated to the client. Further
the servlet is put into service and will not be re-initialized
until the servlet's application is restarted. As a result, the
injection will not be retried until the application is
restarted and, in the meantime, any request for the servlet
which references the resource which failed to inject will
result in a NullPointerException.

A similar problem can happen during filter and listener
initialization.

Note, according to Java EE Specification EE 5.2.4 : If the
container fails to find a resource needed for injection,
initialization of the class must fail, and the class must not
be put into service.

Problem conclusion

The WebContainer code has been updated to propagate injection
exceptions to the client and to write new error messages
(SRVE0319E, SRVE0320E, SRVE0321E, and SRVE0322E) to the server
logs to further explain the failure. Also, the Webcontainer
code has been updated to not put a servlet into service if it
has an injection failure during initialization.

Note to enable propagation of an injection exception to the
client and to not put a servlet into service a new
WebContainer Custom property will need to be set:
com.ibm.ws.webcontainer.ignoreinjectionfailure = false
(default = true)
Please refer to the following technote for instructions on
enabling WebContainer custom properties:
http://www.ibm.com/support/docview.wss?rss=180&uid=swg21284395

For further information on error messages discussed above
please refer IBM WebSphere Application Server Version 7.0
Information Center.

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
PK97815
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-10-02
Closed date
2009-11-10
Last modified date
2009-11-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

PK97815: DO NOT PUT SERVLET IN SERVICE AFTER INJECTION FAILURE.

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?