Uploaded image for project: 'HAL'
  1. HAL
  2. HAL-1839

Properties in the Resource Adapter(IBM MQ) are removed when updating the connection pool with Management Console

XMLWordPrintable

    • Hide

      (1) Setup the Resoruce Adaptor subsystem for IBM MQ

      (I think IBM MQ Server environment is NOT needed for reproduce.)
      1. Get IBM MQ Resource Adapter from IBM site or maven repository.
      2. Copy wmq.jmsra.rar(IBM MQ Resoruce Adapter) to $JBOSS_HOME/standalone/deployments/.

      3. Start EAP like below:
      $ $JBOSS_HOME/bin/standalone.sh -c standalone-full.xml

      4. Configure the Resource Adapter for IBM MQ
      Modify the following value for your env.:

      • <IBM MQ HOST>: IBM MQ Hostname/IP Address
      • <IBM MQ PORT>: IBM MQ Port
      • <QUEUE>: Queue Name
      • <QUEUE MANAGER>: Queue Manager Name
      • <CHANNEL>: Channel Name

      CLI:

      /subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar:add(archive=wmq.jmsra.rar, transaction-support=XATransaction)
/subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar/connection-definitions=mq-cd:add(class-name=com.ibm.mq.connector.outbound.ManagedConnectionFactoryImpl, jndi-name=java:jboss/IBM_MQ_CONNECTION_FACTORY, enabled=true)
/subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar/admin-objects=queue-ao:add(class-name=com.ibm.mq.connector.outbound.MQQueueProxy, jndi-name=java:jboss/<QUEUE>)
/subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar/admin-objects=queue-ao/config-properties=baseQueueName:add(value=<QUEUE>)
/subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar/admin-objects=queue-ao/config-properties=baseQueueManagerName:add(value=<QUEUE MANAGER>)
/subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar/connection-definitions=mq-cd/config-properties=hostName:add(value=<IBM MQ HOST>)
/subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar/connection-definitions=mq-cd/config-properties=port:add(value=<IBM MQ PORT>)
/subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar/connection-definitions=mq-cd/config-properties=channel:add(value=<CHANNEL>)
/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={Quene Manager})
reload

      (2) Reproduce the issue

      1. Access to the below. And check the Config Properties.
      Management Console > Configuration > Subsystem > Resouce Adapters > wmq.jmsra.rar > View > Connection Definitions > mq-cd > Attributes

      2. After that, update the Min/Max Pool Size(.. wmq.jmsra.rar > View > Connection Definitions > mq-cd > Pool).

      3. Check the mq-cd Attributes and standalone.xml.
      You can see the attributes are removed after step 2.

      Show
      (1) Setup the Resoruce Adaptor subsystem for IBM MQ (I think IBM MQ Server environment is NOT needed for reproduce.) 1. Get IBM MQ Resource Adapter from IBM site or maven repository. 2. Copy wmq.jmsra.rar(IBM MQ Resoruce Adapter) to $JBOSS_HOME/standalone/deployments/. 3. Start EAP like below: $ $JBOSS_HOME/bin/standalone.sh -c standalone-full.xml 4. Configure the Resource Adapter for IBM MQ Modify the following value for your env.: <IBM MQ HOST>: IBM MQ Hostname/IP Address <IBM MQ PORT>: IBM MQ Port <QUEUE>: Queue Name <QUEUE MANAGER>: Queue Manager Name <CHANNEL>: Channel Name CLI: /subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar:add(archive=wmq.jmsra.rar, transaction-support=XATransaction) /subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar/connection-definitions=mq-cd:add(class-name=com.ibm.mq.connector.outbound.ManagedConnectionFactoryImpl, jndi-name=java:jboss/IBM_MQ_CONNECTION_FACTORY, enabled=true) /subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar/admin-objects=queue-ao:add(class-name=com.ibm.mq.connector.outbound.MQQueueProxy, jndi-name=java:jboss/<QUEUE>) /subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar/admin-objects=queue-ao/config-properties=baseQueueName:add(value=<QUEUE>) /subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar/admin-objects=queue-ao/config-properties=baseQueueManagerName:add(value=<QUEUE MANAGER>) /subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar/connection-definitions=mq-cd/config-properties=hostName:add(value=<IBM MQ HOST>) /subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar/connection-definitions=mq-cd/config-properties=port:add(value=<IBM MQ PORT>) /subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar/connection-definitions=mq-cd/config-properties=channel:add(value=<CHANNEL>) /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={Quene Manager}) reload (2) Reproduce the issue 1. Access to the below. And check the Config Properties. Management Console > Configuration > Subsystem > Resouce Adapters > wmq.jmsra.rar > View > Connection Definitions > mq-cd > Attributes 2. After that, update the Min/Max Pool Size(.. wmq.jmsra.rar > View > Connection Definitions > mq-cd > Pool). 3. Check the mq-cd Attributes and standalone.xml. You can see the attributes are removed after step 2.

      Before updating the pool of Resource Adapter.
      standalone-full.xml:

      <resource-adapters>
    <resource-adapter id="wmq.jmsra.rar">
        <archive>
            wmq.jmsra.rar
        </archive>
        <transaction-support>XATransaction</transaction-support>
        <connection-definitions>
            <connection-definition class-name="com.ibm.mq.connector.outbound.ManagedConnectionFactoryImpl" jndi-name="java:jboss/CTION_FACTORY" enabled="true" pool-name="{POOL NAME}">
                <config-property name="hostName">{IBM MQ HOSTNAME}</config-property>
                <config-property name="port">{IBM MQ PORT}</config-property>
                <config-property name="channel">{CHANNEL NAME}</config-property>
                <config-property name="transportType">CLIENT</config-property>
                <config-property name="queueManager">{QUEUE MANAGER NAME}</config-property>
            </connection-definition>
        </connection-definitions>
        <admin-objects>
            <admin-object class-name="com.ibm.mq.connector.outbound.MQQueueProxy" jndi-name="java:jboss/{XXXX}" ueue-ao">
                <config-property name="baseQueueName">{QUEUE NAME}</config-property>
                <config-property name="baseQueueManagerName">{QUEUE MANAGER NAME}</config-property>
            </admin-object>
        </admin-objects>
    </resource-adapter>
</resource-adapters>

      After updating Min Pool Size of the Resource Adapter with Management Console.
      standalone-full.xml:

      <resource-adapters>
    <resource-adapter id="wmq.jmsra.rar">
        <archive>
            wmq.jmsra.rar
        </archive>
        <transaction-support>XATransaction</transaction-support>
        <connection-definitions>
            <connection-definition class-name="com.ibm.mq.connector.outbound.ManagedConnectionFactoryImpl" jndi-name="java:jboss/CTION_FACTORY" enabled="true" pool-name="{POOL NAME}">
                <xa-pool>  <<== All config properties were deleted.
                    <min-pool-size>1</min-pool-size>
                </xa-pool>
            </connection-definition>
        </connection-definitions>
        <admin-objects>
            <admin-object class-name="com.ibm.mq.connector.outbound.MQQueueProxy" jndi-name="java:jboss/{XXXX}" ueue-ao">
                <config-property name="baseQueueName">{QUEUE NAME}</config-property>
                <config-property name="baseQueueManagerName">{QUEUE MANAGER NAME}</config-property>
            </admin-object>
        </admin-objects>
    </resource-adapter>
</resource-adapters>

      All config properties were deleted.

      This issue can be reproduced with the latest JBoss EAP 7.4.9.

              lvydra Lukas Vydra
              lvydra Lukas Vydra
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: