[
https://issues.jboss.org/browse/TEIID-3617?page=com.atlassian.jira.plugin...
]
Kylin Soong commented on TEIID-3617:
------------------------------------
Above is NOT scoped to the VDB. Once you scope to the VDB, it may be
not that worth while to put in the system configuration, as that needs to be managed every
time one deploys and undeploys the vdb.
Each time create a session, the 'authentication-max-sessions-allowed-per-user'
will be parse are replace the previous or system level setting, there is no doubt, VDB
properties setting will take effect, and it not effect in deploys/undeploys, and effect in
connection creates/closes. Also write-attribute will totally refresh the setting.
Typically anything teiid scoped is not in the system configuration.
I think authentication-max-sessions-allowed-per-user are more same as
authentication-max-sessions-allowed, as below cli for setting max allowed sessions(default
is 1000)
{code}
/subsystem=teiid:write-attribute(name=authentication-max-sessions-allowed,value=1000)
/subsystem=teiid:read-attribute(name=authentication-max-sessions-allowed)
{code}
why authentication-max-sessions-allowed can add as a attribute, and
authentication-max-sessions-allowed-per-user can't?
Provide an option to Limit per user based connections
-----------------------------------------------------
Key: TEIID-3617
URL:
https://issues.jboss.org/browse/TEIID-3617
Project: Teiid
Issue Type: Feature Request
Components: Server
Reporter: Xian Liu
Assignee: Kylin Soong
Fix For: 9.1
we deploy teiid for users to get data, but some users will create many connections to
teiid and they are not necessary, I need to find a good way to limit each user account can
only get like 50 connections or so
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)