Hide Forgot
This bugzilla is clone from jira: https://issues.jboss.org/browse/JBEAP-558 - and is used for tracking purpose for IBM: WebSphere MQ 8 resource adapter does not accept activation config property "destinationLookup" and "connectionFactoryLookup" If message driven bean with this property is deployed then following warning is logged: 14:57:45,718 WARN [org.jboss.as.ejb3] (MSC service thread 1-6) WFLYEJB0006: ActivationConfigProperty destinationLookup will be ignored since it is not allowed by resource adapter: wmq.jmsra MDB will not any receive messages. TCK 7 test fail because of this issue: [javatest.batch] FAILED........com/sun/ts/tests/jms/ee20/cditests/mdb/Client.java#testCDIInjectionOfMDBWithQueueReplyFromEjb [javatest.batch] FAILED........com/sun/ts/tests/jms/ee20/cditests/mdb/Client.java#testCDIInjectionOfMDBWithTopicReplyFromEjb Customer impact: MDB with activation config property destinationLookup cannot be deployed. Workaround is to use activation config property destination and destinationType.
------- Comment From chavez.com 2016-03-22 10:55 EDT------- Hello, Sorry for the long delay. It took a while to find the L3 team for this particular MQ issue but this is what they had to say: "The problem with missing destinationLookup and connectionFactoryLookup properties is covered by MQ APAR IT11950. The APAR is still in open state but should be ready to close shortly, and will be targeted for inclusion in MQ 8.0.0.6."
Thanks a lot for update! I'll update redhat internal status for this issue.
------- Comment From hannsj_uhl.com 2017-02-06 10:19 EDT------- (In reply to comment #10) > Hello, > > Sorry for the long delay. It took a while to find the L3 team for this > particular MQ issue but this is what they had to say: > > "The problem with missing destinationLookup and connectionFactoryLookup > properties is covered by MQ APAR IT11950. > > The APAR is still in open state but should be ready to close shortly, and > will be targeted for inclusion in MQ 8.0.0.6." . fyi ... IBM MQ Version 8.0 Fix Pack 8.0.0.6 is available since 01/31/2017 ... see http://www-01.ibm.com/support/docview.wss?uid=swg27043086 and http://www-01.ibm.com/support/docview.wss?uid=swg27043086#8006 stating e.g. " IT11950 MQ V8 resource adapter does not support the mdb activation properties connectionfactorylookup and destinationlookup " ...
Thanks for update! I created ticket to install it to our WMQ8 instance. Plan is to certify WMQ 8.0.0.6 RA with EAP 7.1.0.GA.
------- Comment From chavez.com 2017-02-25 21:09 EDT------- (In reply to comment #18) > Thanks for update! I created ticket to install it to our WMQ8 instance. Plan > is to certify WMQ 8.0.0.6 RA with EAP 7.1.0.GA. Hello, Did the certification occur yet? Thanks.
Not yet, certification will be done with EAP 7.1.0.GA. However we might have preliminary results before GA. If there is any outstanding issue than we'll share it as for this issue.
------- Comment From chavez.com 2017-05-08 22:31 EDT------- Any update or estimate on the certification please? Thanks.
There is first attempt to execute it and preliminary results should be available during next 2 weeks. Ondrej Kalman is in charge of this effort. I'll let him to provide more information once he has results and investigation done.
Hi preliminary results are promising. We have found few issues, tracked on https://issues.jboss.org but these are not blockers.
------- Comment From chavez.com 2017-05-30 20:10 EDT------- (In reply to comment #23) > Hi preliminary results are promising. We have found few issues, tracked on > https://issues.jboss.org but these are not blockers. Thanks for the update. When you are satisfied that the original issue reported in this bug has been fixed by the IBM MQ update, let us know so we can close out our bug.
... closing this Red Hat bugzilla per all the previous comments ... ... please open new bugzillas if required ... thanks for your support ...
------- Comment From hannsj_uhl.com 2017-12-06 09:55 EDT------- .