APAR status
Closed as program error.
Error description
The MQ V8 resource adapter has been deployed into a Wildfly V9 application server. A message-driven bean application (MDB) has been installed into the same application server, and has been written to make use of the activation properties: - connectionFactoryLookup - destinationLookup However, when the application starts up, the warning messages: WFLYEJB0006: ActivationConfigProperty destinationLookup will be ignored since it is not allowed by resource adapter: wmq.jmsra WFLYEJB0006: ActivationConfigProperty connectionFactoryLookup will be ignored since it is not allowed by resource adapter: wmq.jmsra appear in the application server's log file and no messages are delivered to the MDB.
Local fix
Instead of using 'destinationLookup': - Set the 'useJNDI' property to the value 'true' - And set the 'destination' property to the JNDI name of the destination to look up.
Problem summary
**************************************************************** USERS AFFECTED: This issue affects users of the MQ V8 Resource Adapter, who have written message-driven bean applications that are using the activation properties: - connectionFactoryLookup - destinationLookup Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: Section 13.1 of the JMS 2.0 Specification contains a table which shows all of the message-driven bean (MDB) activation properties which should be supported by any resource adapter that is included with a JMS 2.0 compliant JMS provider. The properties are shown below: - destinationLookup - connectionFactoryLookup - acknowledgeMode - messageSelector - destinationType - subscriptionDurability - clientId - subscriptionName The resource adapter shipped with MQ V8 only supported the properties shown below: - acknowledgeMode - messageSelector - destinationType - subscriptionDurability - clientId - subscriptionName The properties: - destinationLookup - connectionFactoryLookup were not supported, and could not be used.
Problem conclusion
The MQ V8 resource adapter has been updated to include support for the MDB activation properties: - destinationLookup - connectionFactoryLookup If the MDB activation property connectionFactoryLookup is specified, and both the connection factory in JNDI and the activation specification have the clientID property set, then the value from the activation specification will be used in preference to the value on the connection factory. This allows multiple activation specifications to use the same underlying connection factory in JNDI, and specify different values for the clientID property. For more information about this APAR, please see the following video : https://www.youtube.com/watch?v=rxWc7IF-noY --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v8.0 8.0.0.6 The latest available maintenance can be obtained from 'WebSphere MQ Recommended Fixes' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 If the maintenance level is not yet available information on its planned availability can be found in 'WebSphere MQ Planned Maintenance Release Dates' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 ---------------------------------------------------------------
Temporary fix
Comments
APAR Information
APAR number
IT11950
Reported component name
WMQ BASE MULTIP
Reported component ID
5724H7251
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-10-23
Closed date
2016-03-28
Last modified date
2016-04-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
WMQ BASE MULTIP
Fixed component ID
5724H7251
Applicable component levels
R800 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.0.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
29 April 2016