[ https://issues.jboss.org/browse/TEIIDDES-3046?page=com.atlassian.jira.plu... ] Ramesh Reddy edited comment on TEIIDDES-3046 at 4/17/17 11:47 AM: ------------------------------------------------------------------ In the case of the Resource Adapter the "id" value is used as the identifier, as the life-cycle of the RA is currently NOT managed at the connection level, but at RA level. Typically RA -- * -->ConnectionFactory -- * -->Connections but typical usage has been RA -- 1 -->ConnectionFactory -- * -->Connections [*] = means multiple, [1] = means single connection factory Since WildFly does not provide same level connection factory management at ConnectionFactory level without the restart of the server, the workaround was based on creating a single connection factory per RA. So, now since the pool name is at a different level than the management, Teiid Admin API uses the "id" at the RA as identifier. Even in the case when pool -name is omitted in RA, I am sure one is generated internally for management purposes. Note that this is *may* be true only if you are editing the standalone.xml file directly. If you are using CLI like below {code} /subsystem=resource-adapters/resource-adapter=file/connection-definitions=fileDS:add(jndi-name="${jndi.name}", class-name=org.teiid.resource.adapter.file.FileManagedConnectionFactory, enabled=true, use-java-context=true) {code} Note the "file" and "fileDS" in above code fragment, where "file" becomes the RA's id and "fileDS" becomes the connection-pool name. Since the Teiid Admin API uses the CLI underneath, it may generate some of these names automatically for you. When users mix and match between Designer usage and hand coding they may get into discrepancies, but as long they use single mechanism it should be fine, and 99% of time that is the case. was (Author: rareddy): In the case of the Resource Adapter the "id" value is used as the identifier, as the life-cycle of the RA is currently NOT managed at the connection level, but at RA level. Typically RA --*-->ConnectionFactory --*-->Connections but typical usage has been RA --1-->ConnectionFactory --*-->Connections [*] = means multiple, [1] = means single connection factory Since WildFly does not provide same level connection factory management at ConnectionFactory level without the restart of the server, the workaround was based on creating a single connection factory per RA. So, now since the pool name is at a different level than the management, Teiid Admin API uses the "id" at the RA as identifier. Even in the case when pool -name is omitted in RA, I am sure one is generated internally for management purposes. Note that this is *may* be true only if you are editing the standalone.xml file directly. If you are using CLI like below {code} /subsystem=resource-adapters/resource-adapter=file/connection-definitions=fileDS:add(jndi-name="${jndi.name}", class-name=org.teiid.resource.adapter.file.FileManagedConnectionFactory, enabled=true, use-java-context=true) {code} Note the "file" and "fileDS" in above code fragment, where "file" becomes the RA's id and "fileDS" becomes the connection-pool name. Since the Teiid Admin API uses the CLI underneath, it may generate some of these names automatically for you. When users mix and match between Designer usage and hand coding they may get into discrepancies, but as long they use single mechanism it should be fine, and 99% of time that is the case. -- This message was sent by Atlassian JIRA (v7.2.3#72005)