Loading...

XML

Word

Printable

Type: Bug
Resolution: Duplicate
Priority: Major
Fix Version/s: None
Affects Version/s: 7.3.1.GA
Component/s: Documentation
Labels:
None

CDW devel_ack:
CDW docs_ack:
CDW pm_ack:
CDW qa_ack:
CDW release:
Target Release:

7.3.z.GA
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.

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

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.

is cloned by

WFLY-13503 Websphere MQ Resource Adapter Configuration Does Not Take Effect Until Reboot

Resolved

is documented by

JBEAP-19605 [GSS](7.3.z) WFLY-13503 - Websphere MQ Resource Adapter Configuration Does Not Take Effect Until Reboot

Closed

JBEAP-20578 [7.4.beta][GSS](7.3.z) WFLY-13503 - Websphere MQ Resource Adapter Configuration Does Not Take Effect Until Reboot

Closed

relates to

JBEAP-19064 [QE](7.3.z) WFLY-13375 - JNDI view does not show implementation classes for connection factories and destinations registered by 3rd party resource adapters

Closed

WFLY-13375 JNDI view does not show implementation classes for connection factories and destinations registered by 3rd party resource adapters

Closed

Assignee:: Parul Sharma

Reporter:: Duane Hawkins

Votes:: 0 Vote for this issue

Watchers:: 8 Start watching this issue

Created:: 2020/04/21 1:49 PM

Updated:: 2021/10/24 6:24 AM

Resolved:: 2020/11/12 3:12 PM

Details

Description

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates