Provide a separate Admin connection
-----------------------------------
Key: TEIID-944
URL:
https://jira.jboss.org/jira/browse/TEIID-944
Project: Teiid
Issue Type: Sub-task
Components: AdminApi, Server
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 7.0
Currently the Admin API can be accessed from JDBC API and as well a separate connection on
the same port as the JDBC connection. Since in the container environment the Admin API is
based on the Profile Service this needs to be on its own connection that is subject to the
same authorization checks as of the profile service/jmx-console. It will no longer
available on the JDBC connection.
Although, we can still serve the both connections on same port as the JDBC, by having a
separate port the traffic on the Admin connection can be by default encrypted always, and
the number of IO threads will be limited and do not hog the JDBC connection threads.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira