Fixes are available
PI48971:ActiveMQ properties not being honored in JMSActivationSpec in Liberty
16.0.0.2: WebSphere Application Server Liberty 16.0.0.2
16.0.0.3: WebSphere Application Server Liberty 16.0.0.3
16.0.0.4: WebSphere Application Server Liberty 16.0.0.4
17.0.0.1: WebSphere Application Server Liberty 17.0.0.1
17.0.0.2: WebSphere Application Server Liberty 17.0.0.2
17.0.0.3: WebSphere Application Server Liberty 17.0.0.3
17.0.0.4: WebSphere Application Server Liberty 17.0.0.4
18.0.0.1: WebSphere Application Server Liberty 18.0.0.1
18.0.0.2: WebSphere Application Server Liberty 18.0.0.2
18.0.0.3: WebSphere Application Server Liberty 18.0.0.3
18.0.0.4: WebSphere Application Server Liberty 18.0.0.4
19.0.0.1: WebSphere Application Server Liberty 19.0.0.1
19.0.0.2: WebSphere Application Server Liberty 19.0.0.2
19.0.0.3: WebSphere Application Server Liberty 19.0.0.3
19.0.0.4: WebSphere Application Server Liberty 19.0.0.4
19.0.0.5: WebSphere Application Server Liberty 19.0.0.5
19.0.0.6: WebSphere Application Server Liberty 19.0.0.6
19.0.0.7: WebSphere Application Server Liberty 19.0.0.7
19.0.0.8: WebSphere Application Server Liberty 19.0.0.8
19.0.0.9: WebSphere Application Server Liberty 19.0.0.9
19.0.0.10: WebSphere Application Server Liberty 19.0.0.10
19.0.0.11: WebSphere Application Server Liberty 19.0.0.11
19.0.0.12: WebSphere Application Server Liberty 19.0.0.12
20.0.0.1: WebSphere Application Server Liberty 20.0.0.1
20.0.0.2: WebSphere Application Server Liberty 20.0.0.2
20.0.0.3: WebSphere Application Server Liberty 20.0.0.3
20.0.0.4: WebSphere Application Server Liberty 20.0.0.4
20.0.0.5: WebSphere Application Server Liberty 20.0.0.5
20.0.0.6: WebSphere Application Server Liberty 20.0.0.6
20.0.0.7: WebSphere Application Server Liberty 20.0.0.7
20.0.0.8: WebSphere Application Server Liberty 20.0.0.8
20.0.0.9: WebSphere Application Server Liberty 20.0.0.9
20.0.0.10: WebSphere Application Server Liberty 20.0.0.10
20.0.0.11: WebSphere Application Server Liberty 20.0.0.11
20.0.0.12: WebSphere Application Server Liberty 20.0.0.12
21.0.0.3: WebSphere Application Server Liberty 21.0.0.3
21.0.0.4: WebSphere Application Server Liberty 21.0.0.4
21.0.0.5: WebSphere Application Server Liberty 21.0.0.5
21.0.0.6: WebSphere Application Server Liberty 21.0.0.6
21.0.0.7: WebSphere Application Server Liberty 21.0.0.7
21.0.0.8: WebSphere Application Server Liberty 21.0.0.8
21.0.0.9: WebSphere Application Server Liberty 21.0.0.9
21.0.0.1: WebSphere Application Server Liberty 21.0.0.1
21.0.0.2: WebSphere Application Server Liberty 21.0.0.2
21.0.0.10: WebSphere Application Server Liberty 21.0.0.10
21.0.0.11: WebSphere Application Server Liberty 21.0.0.11
21.0.0.12: WebSphere Application Server Liberty 21.0.0.12
22.0.0.1: WebSphere Application Server Liberty 22.0.0.1
22.0.0.2: WebSphere Application Server Liberty 22.0.0.2
22.0.0.3: WebSphere Application Server Liberty 22.0.0.3
22.0.0.4: WebSphere Application Server Liberty 22.0.0.4
APAR status
Closed as program error.
Error description
javax.resource.spi.InvalidPropertyException errors occur during startup when Websphere Liberty server attempts to connect to ActiveMQ, The following error is written to the SystemOut.log: J2CA8802E: The message endpoint activation failed for resource adapter activemq-rar-5.11.1 due to exception: javax.resource. spi.InvalidPropertyException: Invalid settings: destination is a required field and must be set to the destination name. at org.apache.activemq.ra.ActiveMQActivationSpec.validate (ActiveMQActivationSpec.java:137) at com.ibm.ws.jca.service.EndpointActivationService.create ActivationSpec(EndpointActivationService.java:255) at com.ibm.ws.jca.service.EndpointActivationService.activate Endpoint(EndpointActivationService.java:397) at com.ibm.ws.ejbcontainer.mdb.internal.MessageEndpoint FactoryImpl.activateEndpointInternal(MessageEndpoint FactoryImpl.java:167) at com.ibm.ws.ejbcontainer.mdb.internal.MDBRuntimeImpl. activateEndpoint(MDBRuntimeImpl.java:524) at com.ibm.ws.ejbcontainer.mdb.internal.MDBRuntimeImpl. activatePendingEndpoints(MDBRuntimeImpl.java:389) at com.ibm.ws.ejbcontainer.mdb.internal.MDBRuntimeImpl. setServerStarted(MDBRuntimeImpl.java:263) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:94) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:55) at java.lang.reflect.Method.invoke(Method.java:619) at org.apache.felix.scr.impl.helper.BaseMethod.invoke Method(BaseMethod.java:231)
Local fix
Add the <activation-config> element in the Message Driven Bean(MDB) deployment descriptor
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server Liberty using third party JMS * * resource adapters * **************************************************************** * PROBLEM DESCRIPTION: Various problems seen when using * * destination property configured on * * activation specification * **************************************************************** * RECOMMENDATION: * **************************************************************** The server.xml contains a resource adapter entry for a third party JMS resource adapter such as ActiveMQ or Solace. Various problems may be seen in the logs including: 1. Error J2CA8802E in the console or message log. For example J2CA8802E: The message endpoint activation failed for resource adapter activemq-rar-5.11.1 due to exception: javax.resource.spi.InvalidPropertyException: Invalid settings: destination is a required field and must be set to the destination name. at org.apache.activemq.ra.ActiveMQActivationSpec.validate (ActiveMQActivationSpec.java:137) at com.ibm.ws.jca.service.EndpointActivationService.createActivatio nSpec(EndpointActivationService.java:255) 2. Warning about NullPointerException in the logs, for example [2/18/16 11:37:13:307 CST] 00000027 com.ibm.ws.jca.internal.BootstrapContextImpl W J2CA8500E: An error occurred while attempting to configure a property destination of configuration element com.ibm.ws.jca.adminObject.supertype[MyQueue1] on the class com.solacesystems.jms.ra.outbound.QueueProxy: java.lang.NullPointerException at com.ibm.ws.jca.internal.BootstrapContextImpl.getDestination(Boot strapContextImpl.java:696) at com.ibm.ws.jca.internal.BootstrapContextImpl.configure(Bootstrap ContextImpl.java:401) at com.ibm.ws.jca.service.AdminObjectService.createResource(AdminOb jectService.java:148) at com.ibm.ws.jca.internal.BootstrapContextImpl.getDestination(Boot strapContextImpl.java:729) at com.ibm.ws.jca.internal.BootstrapContextImpl.configure(Bootstrap ContextImpl.java:401) at com.ibm.ws.jca.service.EndpointActivationService.createActivatio nSpec(EndpointActivationService.java:322) at com.ibm.ws.jca.service.EndpointActivationService.activateEndpoin t(EndpointActivationService.java:514) ... 3. destination property value on an activation specification does not match the id or jndiName of an administered object causes CNTR4015W, for example: [WARNING ] CNTR4015W: The message endpoint for the InventoryAdvertiserMDB message-driven bean cannot be activated because the jcastore/InventoryAdvertiserMDB activation specification is not available. The message endpoint will not receive messages until the activation specification becomes available.
Problem conclusion
The code has been updated to correctly process the destination property on activation specifications to eliminate errors and exceptions. While a destination value on an activation specification can still be used to cause an administered object to be configured on the resource adapter by matching the id or jndiName on an administered object, it is no longer required that the destination value match the id or jndiName on an administered object. The fix for this APAR is currently targeted for inclusion in fix pack 16.0.0.2. 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
PI48971
Reported component name
WAS LIBERTY COR
Reported component ID
5725L2900
Reported release
855
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-09-17
Closed date
2016-02-29
Last modified date
2016-06-13
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
WAS LIBERTY COR
Fixed component ID
5725L2900
Applicable component levels
R855 PSY
UP
Document Information
Modified date:
03 May 2022