[
https://issues.jboss.org/browse/TEIID-1387?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-1387:
-------------------------------------
I would like to clarify the JIRA that no "admin" connections are allowed on the
"jdbc" port, and no "jdbc" is allowed on the "admin" port,
no matter what the actual port numbers configured for these services on the Teiid. 31000,
and 31443 are default ports out of the box. The user has can change these.
Restrict access of default port 31000 to JDBC and 31443 to Admin
connections
----------------------------------------------------------------------------
Key: TEIID-1387
URL:
https://issues.jboss.org/browse/TEIID-1387
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 7.1
Reporter: Ramesh Reddy
Assignee: Steven Hawkins
31000 is default connection port intended for JDBC connections. ex:
jdbc:teiid<vdb>@mm://host:31000
31443 is default secured connection port intended for Admin connections ex:
mms://<host>:31443
However, due to lack of restriction in the Teiid server, user can make a JDBC connection
like "jdbc:teiid<vdb>@mms://host:31443", or make an Admin connection like
"mm://localhost:31000" thus creates a confusion as to which form to use
"mm" or "mms" and which port to use "31000" or
"31443".
The reason 31443 originally created was to secure the Admin connections and to create a
separate process thread pool as Admin calls are synchronous. Where are JDBC calls as
asynchronous. Mixing them up might lead confusion and not to mention thread contention
under heavy load. So, Teiid should restrict the use of 31000 to JDBC and 31443 to Admin
traffic.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira