-
Bug
-
Resolution: Done
-
Major
-
None
If connection factory or JMS destination is configured for third party resource adapter (like IBMMQ 8/9, AMQ 6) then the value for registered implementation class is ? - see:
[standalone@localhost:9990 /] /subsystem=naming:jndi-view { "outcome" => "success", "result" => { "java: contexts" => { "java:" => { ... }, "jms" => { "class-name" => "javax.naming.Context", "children" => { "CF" => { "class-name" => "java.lang.Object", "value" => "?" }, "NmvtisSendQ" => { "class-name" => "java.lang.Object", "value" => "?" }, "topic" => { "class-name" => "javax.naming.Context", "children" => { "T1RHEL6X86_64DYNAMICLARGEOPENJDK18" => { "class-name" => "java.lang.Object", "value" => "?" }, "T2RHEL6X86_64DYNAMICLARGEOPENJDK18" => { "class-name" => "java.lang.Object", "value" => "?" } } }
There should be provided valid value, for example com.ibm.mq.connector.outbound.ManagedConnectionFactoryImpl for "CF" connection factory for IBMMQ.
- clones
-
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
- is related to
-
JBEAP-18969 [GSS](7.2.z) WFLY-13375 - JNDI view does not show implementation classes for connection factories and destinations registered by 3rd party resource adapters
- Closed
-
JBEAP-19314 [GSS](7.3.z) WFLY-13503 - Websphere MQ Resource Adapter Configuration Does Not Take Effect Until Reboot
- Closed