[JBoss JIRA] (TEIID-6014) Connection Pooling in SQL server XA data source
by Manoj Majumdar (Jira)
[ https://issues.redhat.com/browse/TEIID-6014?page=com.atlassian.jira.plugi... ]
Manoj Majumdar updated TEIID-6014:
----------------------------------
Description:
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.
was:
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.
Below is sql server data source configuration in standalone-teiid.xml
<xa-datasource jndi-name="java:/XXXX" pool-name="XXXX">
<xa-datasource-property name="DatabaseName">
XXXX
</xa-datasource-property>
<xa-datasource-property name="PortNumber">
XXXX
</xa-datasource-property>
<xa-datasource-property name="ServerName">
XXXX
</xa-datasource-property>
<xa-datasource-property name="URL">
jdbc:sqlserver://127.0.0.1:1433;databaseName=XXXX;sendTimeAsDateTime=false
</xa-datasource-property>
<driver>sqlserver</driver>
<xa-pool>
<min-pool-size>4</min-pool-size>
<max-pool-size>8</max-pool-size>
<flush-strategy>FailingConnectionOnly</flush-strategy>
</xa-pool>
<security>
<user-name>XXXX</user-name>
<password>XXXX</password>
</security>
<validation>
<check-valid-connection-sql>select 1</check-valid-connection-sql>
<validate-on-match>true</validate-on-match>
<background-validation>false</background-validation>
</validation>
</xa-datasource>
Please let us know are we missing any configuration.
> 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)
5 years, 1 month
[JBoss JIRA] (TEIID-6014) Connection Pooling in SQL server XA data source
by Manoj Majumdar (Jira)
[ https://issues.redhat.com/browse/TEIID-6014?page=com.atlassian.jira.plugi... ]
Manoj Majumdar updated TEIID-6014:
----------------------------------
Description:
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.
Below is sql server data source configuration in standalone-teiid.xml
<xa-datasource jndi-name="java:/XXXX" pool-name="XXXX">
<xa-datasource-property name="DatabaseName">
XXXX
</xa-datasource-property>
<xa-datasource-property name="PortNumber">
XXXX
</xa-datasource-property>
<xa-datasource-property name="ServerName">
XXXX
</xa-datasource-property>
<xa-datasource-property name="URL">
jdbc:sqlserver://127.0.0.1:1433;databaseName=XXXX;sendTimeAsDateTime=false
</xa-datasource-property>
<driver>sqlserver</driver>
<xa-pool>
<min-pool-size>4</min-pool-size>
<max-pool-size>8</max-pool-size>
<flush-strategy>FailingConnectionOnly</flush-strategy>
</xa-pool>
<security>
<user-name>XXXX</user-name>
<password>XXXX</password>
</security>
<validation>
<check-valid-connection-sql>select 1</check-valid-connection-sql>
<validate-on-match>true</validate-on-match>
<background-validation>false</background-validation>
</validation>
</xa-datasource>
Please let us know are we missing any configuration.
was:
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.
> 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.
> Below is sql server data source configuration in standalone-teiid.xml
> <xa-datasource jndi-name="java:/XXXX" pool-name="XXXX">
> <xa-datasource-property name="DatabaseName">
> XXXX
> </xa-datasource-property>
> <xa-datasource-property name="PortNumber">
> XXXX
> </xa-datasource-property>
> <xa-datasource-property name="ServerName">
> XXXX
> </xa-datasource-property>
> <xa-datasource-property name="URL">
> jdbc:sqlserver://127.0.0.1:1433;databaseName=XXXX;sendTimeAsDateTime=false
> </xa-datasource-property>
> <driver>sqlserver</driver>
> <xa-pool>
> <min-pool-size>4</min-pool-size>
> <max-pool-size>8</max-pool-size>
> <flush-strategy>FailingConnectionOnly</flush-strategy>
> </xa-pool>
> <security>
> <user-name>XXXX</user-name>
> <password>XXXX</password>
> </security>
> <validation>
> <check-valid-connection-sql>select 1</check-valid-connection-sql>
> <validate-on-match>true</validate-on-match>
> <background-validation>false</background-validation>
> </validation>
> </xa-datasource>
> Please let us know are we missing any configuration.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (TEIID-6014) Connection Pooling in SQL server XA data source
by Manoj Majumdar (Jira)
Manoj Majumdar created TEIID-6014:
-------------------------------------
Summary: 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
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)
5 years, 1 month
[JBoss JIRA] (TEIID-5321) SAP IQ numeric functions corner case differences
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5321?page=com.atlassian.jira.plugi... ]
Steven Hawkins updated TEIID-5321:
----------------------------------
Fix Version/s: Open To Community
(was: Backlog)
> SAP IQ numeric functions corner case differences
> ------------------------------------------------
>
> Key: TEIID-5321
> URL: https://issues.redhat.com/browse/TEIID-5321
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.12.13.6_4
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
> Priority: Minor
> Fix For: Open To Community
>
>
> The following discrepancies in return values of numeric functions are caused by SAP IQ's behaviour.
> # COT(0)
> #* results in OutOfRange error in Teiid
> #* returns NULL in SAP IQ
> # EXP\(n\) - for n < -15
> #* result is 0 in Teiid
> #* result is in SAP IQ
> #** 0 for -15 > n >=-745
> #** NULL for n<=-746
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (TEIID-5523) Allow for xsd schema association with vdb.xml
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5523?page=com.atlassian.jira.plugi... ]
Steven Hawkins edited comment on TEIID-5523 at 8/10/20 3:23 PM:
----------------------------------------------------------------
Moving to a community issue as we're not concentrating on xml moving forward.
was (Author: shawkins):
Moving to a community issue as we're concentrating on xml moving forward.
> Allow for xsd schema association with vdb.xml
> ---------------------------------------------
>
> Key: TEIID-5523
> URL: https://issues.redhat.com/browse/TEIID-5523
> Project: Teiid
> Issue Type: Quality Risk
> Components: Build/Kits
> Reporter: Steven Hawkins
> Priority: Minor
>
> Using Teiid Thorntail an exception is thrown at deployment when I attempt to associate an xsd with the vdb.xml file. This would be helpful to assist with vdb editing.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month