[
https://issues.redhat.com/browse/TEIID-6014?page=com.atlassian.jira.plugi...
]
Steven Hawkins resolved TEIID-6014.
-----------------------------------
Resolution: Explained
Initially 4 connection threads will be active.
Only if the prefill option is specified.
Whenever we are going to use these connections one by one Available
count will decrement.
I think this requires statistics-enabled to be true.
The various methods of adding an xa dataource - adminapi, directly editing the xml, using
the cli, or even the higher level cli xa-datasource-add call - all have a variety of
defaults and assumptions so you should confirm via the cli the ultimate configuration is
as you expect:
/subsystem=datasources/xa-data-source=XXXX:read-resource
Connection Pooling in SQL server XA data source
-----------------------------------------------
Key: TEIID-6014
URL:
https://issues.redhat.com/browse/TEIID-6014
Project: Teiid
Issue Type: Bug
Reporter: Manoj Majumdar
Assignee: Steven Hawkins
Priority: Major
We are implementing connection pooling in the case of XA data source Sql Server.
As per our understanding of the connection pooling mechanism in the teiid, we are
referring below parameter in the Teiid Admin console.
Below are the parameters mentioned in the Data Source Metrics
i) Available count
ii) Active count
iii) Max used
While deploying the XA data source for SQL server, we have configured the min pool size =
4 and max pool size = 8 and below are our understanding and how ideally it should work if
we have implemented the connection pooling. (Please correct our observation)
# Initially 4 connection threads will be active.
# Whenever we are going to use these connections one by one Available count will
decrement.
# When all 8 connections will have used up, we will wait till connection available back
to pool.
Below are the actual observations.
# No changes identified on Admin console.
# On DB level threads are increasing irrespective of max pool size.
# connections are increasing till 12 connections even though max size is 8
Could you please shed more light on below points:
# How SQL server XA datasource connection pooling is working.
# In case of My sql XA datasource its working as expected.
Attaching screenshot for Admin console statistics and DB level thread status.
Please let us know are we missing any configuration.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)