[JBEAP-549] [7.1] WebSphere MQ 8 RA - [TCK] Activation config property destination for MDB must contain only capital letters - JBoss Issue Tracker

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Critical
Resolution: Done
Affects Version/s: 7.0.0.DR6, 7.0.0.DR7
Fix Version/s: 7.1.z.GA
Component/s: Documentation, WebSphereMQ RA
Labels:
- Doc_prio_2
- docs-bulk-52

Target Release:

7.1.z.GA
Git Pull Request:
https://gitlab.cee.redhat.com/red-hat-jboss-enterprise-application-platform-documentation/eap-documentation/merge_requests/4087
Affects:

Documentation (Ref Guide, User Guide, etc.)

Description

WebSphere MQ 8 resource adapter contains limitation related to name of destination in activation config properties. Name of destination with non-capital letters like:

@ActivationConfigProperty(propertyName = "destination", propertyValue = "q"),

will fail with:

13:28:25,129 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 61) MSC000001: Failed to start service jboss.deployment.unit."mdb-1.0-SNAPSHOT.jar".component.SampleMdb.START: org.jboss.msc.service.StartException in service jboss.deployment.unit."mdb-1.0-SNAPSHOT.jar".component.SampleMdb.START: java.lang.RuntimeException: com.ibm.mq.connector.DetailedResourceException: MQJCA0001: An exception occurred in the JMS layer. See the linked exception for details., error code: MQJCA0001 A call to WebSphere MQ classes for JMS caused an exception to be thrown. See the linked exception for details of the failure.

	at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:57) [wildfly-ee-10.0.0.Alpha5-redhat-1.jar:10.0.0.Alpha5-redhat-1]

	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_51]

	at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_51]

	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_51]

	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_51]

	at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_51]

	at org.jboss.threads.JBossThread.run(JBossThread.java:320)

Caused by: java.lang.RuntimeException: com.ibm.mq.connector.DetailedResourceException: MQJCA0001: An exception occurred in the JMS layer. See the linked exception for details., error code: MQJCA0001 A call to WebSphere MQ classes for JMS caused an exception to be thrown. See the linked exception for details of the failure.

	at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.activate(MessageDrivenComponent.java:241)

	at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.start(MessageDrivenComponent.java:211)

	at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54) [wildfly-ee-10.0.0.Alpha5-redhat-1.jar:10.0.0.Alpha5-redhat-1]

	... 6 more

Caused by: com.ibm.mq.connector.DetailedResourceException: MQJCA0001: An exception occurred in the JMS layer. See the linked exception for details., error code: MQJCA0001 A call to WebSphere MQ classes for JMS caused an exception to be thrown. See the linked exception for details of the failure.

	at com.ibm.mq.connector.services.JCAExceptionBuilder.buildException(JCAExceptionBuilder.java:168)

	at com.ibm.mq.connector.services.JCAExceptionBuilder.buildException(JCAExceptionBuilder.java:134)

	at com.ibm.mq.connector.inbound.MessageEndpointDeployment.startDelivery(MessageEndpointDeployment.java:385)

	at com.ibm.mq.connector.inbound.MessageEndpointDeployment.<init>(MessageEndpointDeployment.java:231)

	at com.ibm.mq.connector.ResourceAdapterImpl.endpointActivation(ResourceAdapterImpl.java:531)

	at org.jboss.jca.core.rar.EndpointImpl.activate(EndpointImpl.java:197)

	at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.activate(MessageDrivenComponent.java:239)

	... 8 more

Caused by: com.ibm.msg.client.jms.DetailedInvalidDestinationException: JMSWMQ2008: Failed to open MQ queue 'q'.

JMS attempted to perform an MQOPEN, but WebSphere MQ reported an error.

Use the linked exception to determine the cause of this error. Check that the specified queue and queue manager are defined correctly.

	at com.ibm.msg.client.wmq.common.internal.Reason.reasonToException(Reason.java:496)

	at com.ibm.msg.client.wmq.common.internal.Reason.createException(Reason.java:214)

	at com.ibm.msg.client.wmq.internal.WMQMessageConsumer.checkJmqiCallSuccess(WMQMessageConsumer.java:212)

	at com.ibm.msg.client.wmq.internal.WMQMessageConsumer.checkJmqiCallSuccess(WMQMessageConsumer.java:260)

	at com.ibm.msg.client.wmq.internal.WMQMessageConsumer.checkJmqiCallSuccess(WMQMessageConsumer.java:152)

	at com.ibm.msg.client.wmq.internal.WMQConsumerShadow.initialize(WMQConsumerShadow.java:1183)

	at com.ibm.msg.client.wmq.internal.WMQAsyncConsumerShadow.initialize(WMQAsyncConsumerShadow.java:923)

	at com.ibm.msg.client.wmq.internal.WMQConnectionBrowser.<init>(WMQConnectionBrowser.java:1452)

	at com.ibm.msg.client.wmq.internal.WMQConnection.createConnectionBrowser(WMQConnection.java:827)

	at com.ibm.msg.client.jms.internal.JmsConnectionImpl.createConnectionBrowser(JmsConnectionImpl.java:1195)

	at com.ibm.msg.client.jms.internal.JmsConnectionConsumerImpl.createConnectionBrowser(JmsConnectionConsumerImpl.java:242)

	at com.ibm.msg.client.jms.internal.JmsConnectionConsumerImpl.<init>(JmsConnectionConsumerImpl.java:166)

	at com.ibm.msg.client.jms.internal.JmsConnectionConsumerImpl.<init>(JmsConnectionConsumerImpl.java:109)

	at com.ibm.msg.client.jms.internal.JmsConnectionImpl.createConnectionConsumer(JmsConnectionImpl.java:611)

	at com.ibm.msg.client.jms.internal.JmsXAConnectionImpl.createConnectionConsumer(JmsXAConnectionImpl.java:235)

	at com.ibm.mq.jms.MQConnection.createConnectionConsumer(MQConnection.java:204)

	at com.ibm.mq.connector.inbound.MessageEndpointDeployment.createConnectionConsumer(MessageEndpointDeployment.java:744)

	at com.ibm.mq.connector.inbound.MessageEndpointDeployment.startDeliveryASF(MessageEndpointDeployment.java:424)

	at com.ibm.mq.connector.inbound.MessageEndpointDeployment.startDelivery(MessageEndpointDeployment.java:342)

	... 12 more

Caused by: com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2085' ('MQRC_UNKNOWN_OBJECT_NAME').

	at com.ibm.msg.client.wmq.common.internal.Reason.createException(Reason.java:202)

	... 29 more

13:28:25,144 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "mdb-1.0-SNAPSHOT.jar")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"mdb-1.0-SNAPSHOT.jar\".component.SampleMdb.START" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"mdb-1.0-SNAPSHOT.jar\".component.SampleMdb.START: java.lang.RuntimeException: com.ibm.mq.connector.DetailedResourceException: MQJCA0001: An exception occurred in the JMS layer. See the linked exception for details., error code: MQJCA0001 A call to WebSphere MQ classes for JMS caused an exception to be thrown. See the linked exception for details of the failure.

    Caused by: java.lang.RuntimeException: com.ibm.mq.connector.DetailedResourceException: MQJCA0001: An exception occurred in the JMS layer. See the linked exception for details., error code: MQJCA0001 A call to WebSphere MQ classes for JMS caused an exception to be thrown. See the linked exception for details of the failure.

    Caused by: com.ibm.mq.connector.DetailedResourceException: MQJCA0001: An exception occurred in the JMS layer. See the linked exception for details., error code: MQJCA0001 A call to WebSphere MQ classes for JMS caused an exception to be thrown. See the linked exception for details of the failure.

    Caused by: com.ibm.msg.client.jms.DetailedInvalidDestinationException: JMSWMQ2008: Failed to open MQ queue 'q'.

JMS attempted to perform an MQOPEN, but WebSphere MQ reported an error.

Use the linked exception to determine the cause of this error. Check that the specified queue and queue manager are defined correctly.

    Caused by: com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2085' ('MQRC_UNKNOWN_OBJECT_NAME')."}}

Customer impact:
Customer must use names with capital letters in "destination" activation config property for message driven beans like:

@ActivationConfigProperty(propertyName = "destination", propertyValue = "QUEUE")

Gliffy Diagrams

Attachments

Issue Links

cloned to

JBEAP-14390 [EO12] WebSphere MQ 8 RA - [TCK] Activation config property destination for MDB must contain only capital letters

Closed

is related to

JBEAP-511 WebSphere MQ 8 RA - [TCK] Activation config property destination for MDB cannot contain special characters like &, |, ...

Closed

[7.1] WebSphere MQ 8 RA - [TCK] Activation config property destination for MDB must contain only capital letters

Details

Description

Gliffy Diagrams

Attachments

Issue Links

Activity

People

Dates