-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: 7.0.0.DR6
-
Fix Version/s: 7.1.0.GA
-
Component/s: Documentation
-
Labels:
-
Target Release:
TCK 7 tests:
[javatest.batch] FAILED........com/sun/ts/tests/jms/ee/mdb/mdb_exceptT/MDBClient.java#Test1
|
[javatest.batch] FAILED........com/sun/ts/tests/jms/ee/mdb/mdb_exceptT/MDBClient.java#Test11
|
[javatest.batch] FAILED........com/sun/ts/tests/jms/ee/mdb/mdb_exceptT/MDBClient.java#Test12
|
[javatest.batch] FAILED........com/sun/ts/tests/jms/ee/mdb/mdb_exceptT/MDBClient.java#Test13
|
[javatest.batch] FAILED........com/sun/ts/tests/jms/ee/mdb/mdb_exceptT/MDBClient.java#Test2
|
[javatest.batch] FAILED........com/sun/ts/tests/jms/ee/mdb/mdb_exceptT/MDBClient.java#Test3
|
[javatest.batch] FAILED........com/sun/ts/tests/jms/ee/mdb/mdb_exceptT/MDBClient.java#Test4
|
[javatest.batch] FAILED........com/sun/ts/tests/jms/ee/mdb/mdb_exceptT/MDBClient.java#Test5
|
[javatest.batch] FAILED........com/sun/ts/tests/jms/ee/mdb/mdb_exceptT/MDBClient.java#Test6
|
[javatest.batch] FAILED........com/sun/ts/tests/jms/ee/mdb/mdb_exceptT/MDBClient.java#Test7
|
[javatest.batch] FAILED........com/sun/ts/tests/jms/ee/mdb/mdb_exceptT/MDBClient.java#Test8
|
fail because they're using queue "jms_ee_mdb_mdb_exceptT_MDB_DURABLETXNS_CMT" for destinationName in activation config properties in MDB. Problem is underscore character "_".
If such a MDB is deployed to EAP 7 then following error logged and MDB is not deployed:
[javatest.batch] 2610: 2015-07-27 14:05:07,382 INFO [org.jboss.as.connector.deployers.RaXmlDeployer] (ServerService Thread Pool -- 85) wmq.jmsra.rar: '.
|
[javatest.batch] 2611: 2015-07-27 14:05:07,382 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 85) MSC000001: Failed to start service jboss.deployment.subunit."mdb_exceptT.ear"."mdb_exceptT_ejb.jar".component.MDB_DURABLETXNS_CMT.START: org.jboss.msc.service.StartException in service jboss.deployment.subunit."mdb_exceptT.ear"."mdb_exceptT_ejb.jar".component.MDB_DURABLETXNS_CMT.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.
|
[javatest.batch] 2612: at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:57)
|
[javatest.batch] 2613: at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_51]
|
[javatest.batch] 2614: at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_51]
|
[javatest.batch] 2615: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_51]
|
[javatest.batch] 2616: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_51]
|
[javatest.batch] 2617: at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_51]
|
[javatest.batch] 2618: at org.jboss.threads.JBossThread.run(JBossThread.java:320) [jboss-threads-2.2.1.Final.jar:2.2.1.Final]
|
[javatest.batch] 2619: 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.
|
[javatest.batch] 2620: at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.activate(MessageDrivenComponent.java:241)
|
[javatest.batch] 2621: at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.start(MessageDrivenComponent.java:211)
|
[javatest.batch] 2622: at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54)
|
[javatest.batch] 2623: ... 6 more
|
[javatest.batch] 2624: 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.
|
[javatest.batch] 2625: at com.ibm.mq.connector.services.JCAExceptionBuilder.buildException(JCAExceptionBuilder.java:168)
|
[javatest.batch] 2626: at com.ibm.mq.connector.services.JCAExceptionBuilder.buildException(JCAExceptionBuilder.java:134)
|
[javatest.batch] 2627: at com.ibm.mq.connector.inbound.MessageEndpointDeployment.startDelivery(MessageEndpointDeployment.java:385)
|
[javatest.batch] 2628: at com.ibm.mq.connector.inbound.MessageEndpointDeployment.<init>(MessageEndpointDeployment.java:231)
|
[javatest.batch] 2629: at com.ibm.mq.connector.ResourceAdapterImpl.endpointActivation(ResourceAdapterImpl.java:531)
|
[javatest.batch] 2630: at org.jboss.jca.core.rar.EndpointImpl.activate(EndpointImpl.java:197)
|
[javatest.batch] 2631: at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.activate(MessageDrivenComponent.java:239)
|
[javatest.batch] 2632: ... 8 more
|
[javatest.batch] 2633: Caused by: com.ibm.msg.client.jms.DetailedInvalidDestinationException: JMSWMQ2008: Failed to open MQ queue 'jms_ee_mdb_mdb_exceptT_MDB_DURABLETXNS_CMT'.
|
[javatest.batch] 2634: JMS attempted to perform an MQOPEN, but WebSphere MQ reported an error.
|
[javatest.batch] 2635: Use the linked exception to determine the cause of this error. Check that the specified queue and queue manager are defined correctly.
|
[javatest.batch] 2636: at com.ibm.msg.client.wmq.common.internal.Reason.reasonToException(Reason.java:496)
|
[javatest.batch] 2637: at com.ibm.msg.client.wmq.common.internal.Reason.createException(Reason.java:214)
|
[javatest.batch] 2638: at com.ibm.msg.client.wmq.internal.WMQMessageConsumer.checkJmqiCallSuccess(WMQMessageConsumer.java:212)
|
[javatest.batch] 2639: at com.ibm.msg.client.wmq.internal.WMQMessageConsumer.checkJmqiCallSuccess(WMQMessageConsumer.java:260)
|
[javatest.batch] 2640: at com.ibm.msg.client.wmq.internal.WMQMessageConsumer.checkJmqiCallSuccess(WMQMessageConsumer.java:152)
|
[javatest.batch] 2641: at com.ibm.msg.client.wmq.internal.WMQConsumerShadow.initialize(WMQConsumerShadow.java:1183)
|
[javatest.batch] 2642: at com.ibm.msg.client.wmq.internal.WMQAsyncConsumerShadow.initialize(WMQAsyncConsumerShadow.java:923)
|
[javatest.batch] 2643: at com.ibm.msg.client.wmq.internal.WMQConnectionBrowser.<init>(WMQConnectionBrowser.java:1452)
|
[javatest.batch] 2644: at com.ibm.msg.client.wmq.internal.WMQConnection.createConnectionBrowser(WMQConnection.java:827)
|
[javatest.batch] 2645: at com.ibm.msg.client.jms.internal.JmsConnectionImpl.createConnectionBrowser(JmsConnectionImpl.java:1195)
|
[javatest.batch] 2646: at com.ibm.msg.client.jms.internal.JmsConnectionConsumerImpl.createConnectionBrowser(JmsConnectionConsumerImpl.java:242)
|
[javatest.batch] 2647: at com.ibm.msg.client.jms.internal.JmsConnectionConsumerImpl.<init>(JmsConnectionConsumerImpl.java:166)
|
[javatest.batch] 2648: at com.ibm.msg.client.jms.internal.JmsConnectionConsumerImpl.<init>(JmsConnectionConsumerImpl.java:109)
|
[javatest.batch] 2649: at com.ibm.msg.client.jms.internal.JmsConnectionImpl.createConnectionConsumer(JmsConnectionImpl.java:611)
|
[javatest.batch] 2650: at com.ibm.mq.jms.MQConnection.createConnectionConsumer(MQConnection.java:204)
|
[javatest.batch] 2651: at com.ibm.mq.connector.inbound.MessageEndpointDeployment.createConnectionConsumer(MessageEndpointDeployment.java:744)
|
[javatest.batch] 2652: at com.ibm.mq.connector.inbound.MessageEndpointDeployment.startDeliveryASF(MessageEndpointDeployment.java:424)
|
[javatest.batch] 2653: at com.ibm.mq.connector.inbound.MessageEndpointDeployment.startDelivery(MessageEndpointDeployment.java:342)
|
[javatest.batch] 2654: ... 12 more
|
[javatest.batch] 2655: Caused by: com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2085' ('MQRC_UNKNOWN_OBJECT_NAME').
|
[javatest.batch] 2656: at com.ibm.msg.client.wmq.common.internal.Reason.createException(Reason.java:202)
|
[javatest.batch] 2657: ... 28 more
|
Customer impact:
Customer cannot deploy MDB with special characters like _, &, | in destination activation config property.
- relates to
-
JBEAP-549 [7.1] WebSphere MQ 8 RA - [TCK] Activation config property destination for MDB must contain only capital letters
-
- Closed
-