[teiid-issues] [JBoss JIRA] Resolved: (TEIID-578) Having max pool connections and max threads as connector properties is confusing

Wed May 13 00:10:46 EDT 2009

     [ https://jira.jboss.org/jira/browse/TEIID-578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins resolved TEIID-578.
----------------------------------

    Resolution: Done

Updated the connection pooling and connector logic to use the ConnectorMaxConnections setting.

> Having max pool connections and max threads as connector properties is confusing
> --------------------------------------------------------------------------------
>
>                 Key: TEIID-578
>                 URL: https://jira.jboss.org/jira/browse/TEIID-578
>             Project: Teiid
>          Issue Type: Quality Risk
>          Components: Connector API
>    Affects Versions: 6.0.0
>            Reporter: Steven Hawkins
>            Assignee: Steven Hawkins
>             Fix For: 6.1.0
>
>
> After talking over connection pool monitoring, it was desirable to make connector configuration easier to understand.  A simple change that will alleviate much confusion is to remove the max pool connections property and to change ConnectorMaxThreads to be "Connector Max Concurrent Connections".  If it's a synch connector "Connector Max Concurrent Connections" is the max number of connections in the pool (if pooled) and is also the max number of threads allowed.  
> If asynch (and thus not pooled), "Connector Max Concurrent Connections" still acts as the max threads setting, which limits the number of connections that can be concurrently used.  The absolute max number of connections may grow higher than max concurrent connections depending on the number of asynch operations performed.

-- 
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