[ https://issues.jboss.org/browse/TEIIDDES-2174?page=com.atlassian.jira.plu... ] Jeff Bride edited comment on TEIIDDES-2174 at 1/22/15 11:06 AM: ---------------------------------------------------------------- Thanks Barry. Even with this JDBC port discovery feature, the inability to manually modify the port in the Teiid Designer is going to remain a problem in some use cases. As an example, in support of JDV training, i have JDV 6.1 running as a docker containers for students on remote hosts. Because Docker sets up its own internal network, selective EAP and JDV ports are proxied through the remote host operating system. ie: in my case, 31000 is proxied through port 32000. In this case, remote JDBC clients connect through 32000 and not 31000 . There is no way that jdbc port discovery running within the EAP/JDV runtime would be aware of the port proxying that is occurring. Requesting the ability to manually over-ride (through the Teiid Deisgner GUI and not the underlying XML in the user's JBDS workspace) the JDBC port. thanks again. jeff was (Author: jbride): Thanks Barry. Even with this JDBC port discovery feature, the inability to manually modify the port in the Teiid Designer is going to remain a problem in some use cases. As an example, in support of JDV training, i have JDV 6.1 running as a docker containers for students on remote hosts. Because Docker sets up its own internal network, selective EAP and JDV ports are proxied through the remote host operating system. ie: in my case, 31000 is proxied through port 32000. In this case, remote JDBC clients connect through 32000 and not 31000 . Requesting the ability to manually over-ride (through the Teiid Deisgner GUI and not the underlying XML in the user's JBDS workspace) the JDBC port. thanks again. jeff -- This message was sent by Atlassian JIRA (v6.3.11#6341)