Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-13503

Websphere MQ Resource Adapter Configuration Does Not Take Effect Until Reboot

    Details

    • Steps to Reproduce:
      Hide
      • Install and patch JBoss EAP 7.2.
      • Start JBoss using the standalone profile (standalone.xml)
      • Log into the jboss-cli
      • Follow the instructions in the reference to deploy the WMQ adapter and configure. Example:
      /subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar:add(archive=wmq.jmsra.rar, transaction-support=NoTransaction)
      
      /subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar/admin-objects=queue-ao:add(class-name=com.ibm.mq.connector.outbound.MQQueueProxy, jndi-name=jms/TEST.Q.IN)
      
      /subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar/admin-objects=queue-ao/config-properties=baseQueueName:add(value=TEST.Q.IN)
      
      /subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar/admin-objects=queue-ao/config-properties=baseQueueManagerName:add(value=JMS.QUEUE.MANAGER)
      
      
      /subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar/admin-objects=queue-ab:add(class-name=com.ibm.mq.connector.outbound.MQQueueProxy, jndi-name=jms/TEST.Q.OUT)
      
      /subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar/admin-objects=queue-ab/config-properties=baseQueueName:add(value=TEST.Q.OUT)
      
      /subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar/admin-objects=queue-ab/config-properties=baseQueueManagerName:add(value=JMS.QUEUE.MANAGER)
      
      /subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar/connection-definitions=mq-cd:add(class-name=com.ibm.mq.connector.outbound.ManagedConnectionFactoryImpl, jndi-name=jms/MQCF, tracking=false)
      
      /subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar/connection-definitions=mq-cd/config-properties=hostName:add(value=192.168.100.104)
      
      /subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar/connection-definitions=mq-cd/config-properties=port:add(value=1814)
      
      /subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar/connection-definitions=mq-cd/config-properties=channel:add(value=JMS.SVRCONN)
      
      /subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar/connection-definitions=mq-cd/config-properties=transportType:add(value=CLIENT)
      
      /subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar/connection-definitions=mq-cd/config-properties=queueManager:add(value=JMS.QUEUE.MANAGER)
      

      List the jndi entries for the container:

      /subsystem=naming:jndi-view
      

      No JNDI entries are present for the queue or connection factory objects.

      Restart the container and login to the jboss-cli and rerun the jndi query

      Now entries are visible.

      Show
      Install and patch JBoss EAP 7.2. Start JBoss using the standalone profile (standalone.xml) Log into the jboss-cli Follow the instructions in the reference to deploy the WMQ adapter and configure. Example: /subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar:add(archive=wmq.jmsra.rar, transaction-support=NoTransaction) /subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar/admin-objects=queue-ao:add( class- name=com.ibm.mq.connector.outbound.MQQueueProxy, jndi-name=jms/TEST.Q.IN) /subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar/admin-objects=queue-ao/config-properties=baseQueueName:add(value=TEST.Q.IN) /subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar/admin-objects=queue-ao/config-properties=baseQueueManagerName:add(value=JMS.QUEUE.MANAGER) /subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar/admin-objects=queue-ab:add( class- name=com.ibm.mq.connector.outbound.MQQueueProxy, jndi-name=jms/TEST.Q.OUT) /subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar/admin-objects=queue-ab/config-properties=baseQueueName:add(value=TEST.Q.OUT) /subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar/admin-objects=queue-ab/config-properties=baseQueueManagerName:add(value=JMS.QUEUE.MANAGER) /subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar/connection-definitions=mq-cd:add( class- name=com.ibm.mq.connector.outbound.ManagedConnectionFactoryImpl, jndi-name=jms/MQCF, tracking= false ) /subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar/connection-definitions=mq-cd/config-properties=hostName:add(value=192.168.100.104) /subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar/connection-definitions=mq-cd/config-properties=port:add(value=1814) /subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar/connection-definitions=mq-cd/config-properties=channel:add(value=JMS.SVRCONN) /subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar/connection-definitions=mq-cd/config-properties=transportType:add(value=CLIENT) /subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar/connection-definitions=mq-cd/config-properties=queueManager:add(value=JMS.QUEUE.MANAGER) List the jndi entries for the container: /subsystem=naming:jndi-view No JNDI entries are present for the queue or connection factory objects. Restart the container and login to the jboss-cli and rerun the jndi query Now entries are visible.

      Description

      When configuring the IBM Websphere Resource Adapter in JBoss 7.2.4 via the jboss-cli according to the directions in:

       https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.2/html/configuring_messaging/resource_adapters#deploy_the_ibm_mq_resource_adapter
      

      No JNDI entries are created for the connection factory and destination objects until the container is restarted. The documentation does not mention a restart being required to initialize the adapter and associated objects.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  parsharma Parul Sharma
                  Reporter:
                  parsharma Parul Sharma
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated: