Fixes are available
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
The CDI interceptor is not triggered for the onMessage() method in a MessageDrivenBean. The only interceptor that is triggered is the EJB interceptor. @CDIInterceptorBinding @Interceptors({EJBInterceptor.class}) public void onMessage(Message inMessage) {:} Logs show: [2015-06-02 07:46:50:026 CEST] 00000085 EJSContainer > EJBinvokeProceed(0:timerMethod) Entry [2015-06-02 07:46:50:026 CEST] 00000085 PrivExAction W J2CA0144W: No mappingConfigAlias found for ConnectionFactory or DataSource jms/MyDataSource. [2015-06-02 07:46:50:026 CEST] 00000085 PrivExAction W J2CA0114W: No container-managed authentication alias found for ConnectionFactory or DataSource jms/MyDataSource. [2015-06-02 07:46:50:135 CEST] 00000085 SystemOut O >>> TestTimerEJB: Sending message: Test message [2015-06-02 07:46:50:135 CEST] 00000085 EJSContainer < EJBinvokeProceed(0:timerMethod) returning null Exit
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server * **************************************************************** * PROBLEM DESCRIPTION: An interceptor declared against an * * message driven bean does not fire * **************************************************************** * RECOMMENDATION: * **************************************************************** An interceptor declared against an message driven bean does not fire. Because of the type hirarchy message driven beans were not considered valid targets for interceptors.
Problem conclusion
The relevent code was changed to include message driven beans. The fix for this APAR is currently targeted for inclusion in fix packs 8.0.0.13 and 8.5.5.10. 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
PI47334
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-08-21
Closed date
2016-02-03
Last modified date
2016-02-03
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
R700 PSY
UP
R850 PSY
UP
Document Information
Modified date:
28 April 2022