Fixes are available
8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
APAR status
Closed as program error.
Error description
While evaluating a PostConstruct annotation on a class which is intended to be an interceptor class, an exception is thrown with message "parameters were specified, but null was the expected comparison at com.ibm.ws.amm.validate.common.lifecycle.BaseLifecycleValidator. validateCommon(BaseLifecycleValidator.java:114)
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V8.0 and V8.5 with enterprise * * applications containing an EJB lifecycle * * annotation (for example @PostConstruct, * * @PreDestroy, @PostActivate, or * * @PrePassivate.) * **************************************************************** * PROBLEM DESCRIPTION: An exception is displayed in * * SystemOut.log with the message: * * "parameters were specified, but null * * was the expected comparison at * * com.ibm.ws.amm.validate.common.lifecycl * * e.BaseLifecycleValidator. * * validateCommon(BaseLifecycleValidator.j * * ava:114) * **************************************************************** * RECOMMENDATION: * **************************************************************** The application server, incorrectly processed an EJB lifecycle method annotation as if it were in a bean class, and therefore following specification rules it expected the associated method to contain zero parameters. However, since the method contained one parameter, an error message was displayed. The code should have recognized that the annotation was not in a bean class, and without anything to identify the class as an interceptor class, it should have skipped validation of the EJB lifecycle method annotation. An EJB lifecycle annotation must be in an interceptor class or in a bean class. A class may be written with the intention of being an interceptor class, but in order for it to be recognized as an interceptor class by the application server, the class must be referenced in an @Interceptors(...) annotation. An interceptor class may also be specified using an @Interceptor annotation. However, the @Interceptor annotation is not supported by WebSphere Application Server and is ignored.
Problem conclusion
The code has been updated to ignore EJB lifecycle annotations in a class that is neither an interceptor class nor a bean class. The fix for this APAR is currently targeted for inclusion in fix packs 8.0.0.5 and 8.5.0.1. 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
PM65629
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-05-28
Closed date
2012-06-29
Last modified date
2012-07-17
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
R800 PSY
UP
R850 PSY
UP
Document Information
Modified date:
28 October 2021