Created attachment 909628 [details] Resource-adapter rar Description of problem: Resource-adapter with same archive names create issues. when attempting to view information about them in the admin console, we cannot view information about the second one because they are seemingly referenced in the admin console by archive name rather than the name of the resource adapter itself. Version-Release number of selected component (if applicable): Steps to Reproduce: When we add two resource-adapters with the same archive -------------------------------------------------------------------------------- /subsystem=resource-adapters/resource-adapter=MQ:add(archive=wmq.jmsra.rar) /subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar:add(archive=wmq.jmsra.rar,transaction-support=XATransaction) -------------------------------------------------------------------------------- when attempting to view information about them in the admin console, we cannot view information about the second one because they are seemingly referenced in the admin console by archive name rather than the name of the resource adapter itself. To reproduce this, add the following two destinations: -------------------------------------------------------------------------------- /subsystem=resource-adapters/resource-adapter=MQ/admin-objects=jms-mqtest1:add(\ class-name=com.ibm.mq.connector.outbound.MQQueueProxy,\ jndi-name="java:/jms/TEST1",\ use-java-context=true\ ) /subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar/admin-objects=jms-mqtest2:add(\ class-name=com.ibm.mq.connector.outbound.MQQueueProxy,\ jndi-name="java:/jms/TEST2",\ use-java-context=true\ ) --------------------------------------------------------------------------------and try to view each of the admin objects in the admin-console: subsystems->connector->resource adapters->wmq.jmsra.rar (pick one or the other)->view->admin objects We will not be able to view one of the admin objects, and the other will show up incorrectly under both resource adapters.
Harald Pehl <hpehl> updated the status of jira HAL-430 to Coding In Progress
Harald Pehl <hpehl> updated the status of jira HAL-430 to Resolved
Verified 6.4.0.DR5
Will the fix be available for 6.3? Customer who reported the defect is requesting it. Thanks.
BZ1150438 is a backport of this issue for 6.3.z