[JBoss JIRA] (TEIIDSB-205) Missing dependencies from the dependencyManagement section
by Van Halbert (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-205?page=com.atlassian.jira.plug... ]
Van Halbert updated TEIIDSB-205:
--------------------------------
Description:
Missing the following dependencies from the dependencyManagement section:
- jakarta.xml.bind:jakarta.xml.bind-api:2.3.3
- jakarta.persistence:jakarta.persistence-api:2.2.3
- org.ow2.asm:asm:5.0.4
was:
Missing the following dependencies from the dependencyManagement section:
- jakarta.xml.bind:jakarta.xml.bind-api:2.3.3
- jakarta.persistence:jakarta.persistence-api:2.2.3
> Missing dependencies from the dependencyManagement section
> ----------------------------------------------------------
>
> Key: TEIIDSB-205
> URL: https://issues.redhat.com/browse/TEIIDSB-205
> Project: Teiid Spring Boot
> Issue Type: Quality Risk
> Components: core
> Affects Versions: 1.5.0
> Reporter: Van Halbert
> Assignee: Van Halbert
> Priority: Major
>
> Missing the following dependencies from the dependencyManagement section:
> - jakarta.xml.bind:jakarta.xml.bind-api:2.3.3
> - jakarta.persistence:jakarta.persistence-api:2.2.3
> - org.ow2.asm:asm:5.0.4
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 11 months
[JBoss JIRA] (TEIIDSB-205) Missing dependencies from the dependencyManagement section
by Van Halbert (Jira)
Van Halbert created TEIIDSB-205:
-----------------------------------
Summary: Missing dependencies from the dependencyManagement section
Key: TEIIDSB-205
URL: https://issues.redhat.com/browse/TEIIDSB-205
Project: Teiid Spring Boot
Issue Type: Quality Risk
Components: core
Affects Versions: 1.5.0
Reporter: Van Halbert
Assignee: Van Halbert
Missing the following dependencies from the dependencyManagement section:
- jakarta.xml.bind:jakarta.xml.bind-api:2.3.3
- jakarta.persistence:jakarta.persistence-api:2.2.3
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 11 months
[JBoss JIRA] (TEIID-5963) Teiid imported all schemas from PG
by Renat Eskenin (Jira)
[ https://issues.redhat.com/browse/TEIID-5963?page=com.atlassian.jira.plugi... ]
Renat Eskenin updated TEIID-5963:
---------------------------------
Steps to Reproduce:
We have teiid spring boot app with jdbc connection.
DDL file
{code:sql}
CREATE DATABASE db;
USE DATABASE db;
--use translator
CREATE FOREIGN DATA WRAPPER postgresql;
--CREATE FOREIGN DATA WRAPPER mypostgresql type postgresql OPTIONS (supportsOrderBy true);
--create teiid server
CREATE SERVER pgserver FOREIGN DATA WRAPPER postgresql OPTIONS (supportsOrderBy true);
-- create source schema
CREATE SCHEMA schpostgresql SERVER pgserver;
-- schema manual_loads
IMPORT FOREIGN SCHEMA manual_loads FROM SERVER pgserver INTO schpostgresql OPTIONS("importer.useFullSchemaName" 'false', "importer.tableTypes" 'TABLE,VIEW');
{code}
Properties
{code}
spring.datasource.platform=pgserver
spring.datasource.driver-class-name=org.postgresql.Driver
spring.datasource.jdbcUrl=jdbc:postgresql://test.com:5432/dwh?SearchPath=manual_loads,currentSchema=manual_loads
spring.datasource.password=
spring.datasource.username=
spring.jpa.properties.hibernate.default_schema=manual_loads
spring.datasource.hikari.schema=manual_loads
hibernate.temp.use_jdbc_metadata_defaults=false
spring.jpa.properties.hibernate.temp.use_jdbc_metadata_defaults=false
logging.level.org=TRACE
spring.jpa.hibernate.ddl-auto=none
spring.main.allow-bean-definition-overriding=true
spring.main.banner-mode=off
spring.profiles.active=dev
teiid.vdb-file=dwh.ddl
{code}
In logs we saw that Teeiid load all metadata from DB not only concrete schema
{code}
FE=> Sync
<=BE BindComplete [unnamed]
<=BE DataRow(len=2)
<=BE CommandStatus(SELECT 1)
<=BE ReadyForQuery(I)
simple execute, handler=org.postgresql.jdbc.PgStatement$StatementResultHandler@8301268, maxRows=0, fetchSize=0, flags=16
FE=> Bind(stmt=S_1,portal=null,$1=<'_xuotedocument'>,type=VARCHAR)
FE=> Execute(portal=null,limit=0)
FE=> Sync
<=BE BindComplete [unnamed]
<=BE DataRow(len=2)
<=BE CommandStatus(SELECT 1)
<=BE ReadyForQuery(I)
simple execute, handler=org.postgresql.jdbc.PgStatement$StatementResultHandler@3bbb53f6, maxRows=0, fetchSize=0, flags=16
FE=> Bind(stmt=S_1,portal=null,$1=<'_xuotelineitem'>,type=VARCHAR)
FE=> Execute(portal=null,limit=0)
FE=> Sync
<=BE BindComplete [unnamed]
<=BE DataRow(len=2)
<=BE CommandStatus(SELECT 1)
<=BE ReadyForQuery(I)
{code}
So, we have loooong start time of app :)
was:
We have teiid spring boot app with jdbc connection.
DDL file
{code:sql}
CREATE DATABASE db;
USE DATABASE db;
--use translator
CREATE FOREIGN DATA WRAPPER postgresql;
--CREATE FOREIGN DATA WRAPPER mypostgresql type postgresql OPTIONS (supportsOrderBy true);
--create teiid server
CREATE SERVER pgserver FOREIGN DATA WRAPPER postgresql OPTIONS (supportsOrderBy true);
-- create source schema
CREATE SCHEMA schpostgresql SERVER pgserver;
-- schema manual_loads
IMPORT FOREIGN SCHEMA manual_loads FROM SERVER pgserver INTO schpostgresql OPTIONS("importer.useFullSchemaName" 'false', "importer.tableTypes" 'TABLE,VIEW');
{code}
Properties
{code}
spring.datasource.platform=pgserver
spring.datasource.driver-class-name=org.postgresql.Driver
spring.datasource.jdbcUrl=jdbc:postgresql://test.com:5432/dwh?SearchPath=manual_loads,currentSchema=manual_loads
spring.datasource.password=
spring.datasource.username=
spring.jpa.properties.hibernate.default_schema=manual_loads
spring.datasource.hikari.schema=manual_loads
hibernate.temp.use_jdbc_metadata_defaults=false
spring.jpa.properties.hibernate.temp.use_jdbc_metadata_defaults=false
logging.level.org=TRACE
spring.jpa.hibernate.ddl-auto=none
spring.main.allow-bean-definition-overriding=true
spring.main.banner-mode=off
spring.profiles.active=dev
teiid.vdb-file=dwh.ddl
{code}
In logs we saw that Teeiid load all metadata from DB not only concrete schema
{code}
FE=> Sync
<=BE BindComplete [unnamed]
<=BE DataRow(len=2)
<=BE CommandStatus(SELECT 1)
<=BE ReadyForQuery(I)
simple execute, handler=org.postgresql.jdbc.PgStatement$StatementResultHandler@8301268, maxRows=0, fetchSize=0, flags=16
FE=> Bind(stmt=S_1,portal=null,$1=<'_xuotedocument'>,type=VARCHAR)
FE=> Execute(portal=null,limit=0)
FE=> Sync
<=BE BindComplete [unnamed]
<=BE DataRow(len=2)
<=BE CommandStatus(SELECT 1)
<=BE ReadyForQuery(I)
simple execute, handler=org.postgresql.jdbc.PgStatement$StatementResultHandler@3bbb53f6, maxRows=0, fetchSize=0, flags=16
FE=> Bind(stmt=S_1,portal=null,$1=<'_xuotelineitem'>,type=VARCHAR)
FE=> Execute(portal=null,limit=0)
FE=> Sync
<=BE BindComplete [unnamed]
<=BE DataRow(len=2)
<=BE CommandStatus(SELECT 1)
<=BE ReadyForQuery(I)
{code}
So, we have loooogn start time of app :)
> Teiid imported all schemas from PG
> ----------------------------------
>
> Key: TEIID-5963
> URL: https://issues.redhat.com/browse/TEIID-5963
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 12.3.1
> Reporter: Renat Eskenin
> Assignee: Steven Hawkins
> Priority: Major
>
> When we started teiid spring boot app, we have long start time.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 11 months
[JBoss JIRA] (TEIID-5963) Teiid imported all schemas from PG
by Renat Eskenin (Jira)
[ https://issues.redhat.com/browse/TEIID-5963?page=com.atlassian.jira.plugi... ]
Renat Eskenin updated TEIID-5963:
---------------------------------
Steps to Reproduce:
We have teiid spring boot app with jdbc connection.
DDL file
{code:sql}
CREATE DATABASE db;
USE DATABASE db;
--use translator
CREATE FOREIGN DATA WRAPPER postgresql;
--CREATE FOREIGN DATA WRAPPER mypostgresql type postgresql OPTIONS (supportsOrderBy true);
--create teiid server
CREATE SERVER pgserver FOREIGN DATA WRAPPER postgresql OPTIONS (supportsOrderBy true);
-- create source schema
CREATE SCHEMA schpostgresql SERVER pgserver;
-- schema manual_loads
IMPORT FOREIGN SCHEMA manual_loads FROM SERVER pgserver INTO schpostgresql OPTIONS("importer.useFullSchemaName" 'false', "importer.tableTypes" 'TABLE,VIEW');
{code}
Properties
{code}
spring.datasource.platform=pgserver
spring.datasource.driver-class-name=org.postgresql.Driver
spring.datasource.jdbcUrl=jdbc:postgresql://test.com:5432/dwh?SearchPath=manual_loads,currentSchema=manual_loads
spring.datasource.password=
spring.datasource.username=
spring.jpa.properties.hibernate.default_schema=manual_loads
spring.datasource.hikari.schema=manual_loads
hibernate.temp.use_jdbc_metadata_defaults=false
spring.jpa.properties.hibernate.temp.use_jdbc_metadata_defaults=false
logging.level.org=TRACE
spring.jpa.hibernate.ddl-auto=none
spring.main.allow-bean-definition-overriding=true
spring.main.banner-mode=off
spring.profiles.active=dev
teiid.vdb-file=dwh.ddl
{code}
In logs we saw that Teeiid load all metadata from DB not only concrete schema
{code}
FE=> Sync
<=BE BindComplete [unnamed]
<=BE DataRow(len=2)
<=BE CommandStatus(SELECT 1)
<=BE ReadyForQuery(I)
simple execute, handler=org.postgresql.jdbc.PgStatement$StatementResultHandler@8301268, maxRows=0, fetchSize=0, flags=16
FE=> Bind(stmt=S_1,portal=null,$1=<'_xuotedocument'>,type=VARCHAR)
FE=> Execute(portal=null,limit=0)
FE=> Sync
<=BE BindComplete [unnamed]
<=BE DataRow(len=2)
<=BE CommandStatus(SELECT 1)
<=BE ReadyForQuery(I)
simple execute, handler=org.postgresql.jdbc.PgStatement$StatementResultHandler@3bbb53f6, maxRows=0, fetchSize=0, flags=16
FE=> Bind(stmt=S_1,portal=null,$1=<'_xuotelineitem'>,type=VARCHAR)
FE=> Execute(portal=null,limit=0)
FE=> Sync
<=BE BindComplete [unnamed]
<=BE DataRow(len=2)
<=BE CommandStatus(SELECT 1)
<=BE ReadyForQuery(I)
{code}
So, we have loooogn start time of app :)
was:
We have teiid spring boot app with jdbc connection.
DDL file
{code:sql}
CREATE DATABASE db;
USE DATABASE db;
--use translator
CREATE FOREIGN DATA WRAPPER postgresql;
--CREATE FOREIGN DATA WRAPPER mypostgresql type postgresql OPTIONS (supportsOrderBy true);
--create teiid server
CREATE SERVER pgserver FOREIGN DATA WRAPPER postgresql OPTIONS (supportsOrderBy true);
-- create source schema
CREATE SCHEMA schpostgresql SERVER pgserver;
-- schema manual_loads
IMPORT FOREIGN SCHEMA manual_loads FROM SERVER pgserver INTO schpostgresql OPTIONS("importer.useFullSchemaName" 'false', "importer.tableTypes" 'TABLE,VIEW');
{code}
Properties
{code}
spring.datasource.platform=pgserver
spring.datasource.driver-class-name=org.postgresql.Driver
spring.datasource.jdbcUrl=jdbc:postgresql://test.com:5432/dwh?SearchPath=manual_loads,currentSchema=manual_loads
spring.datasource.password=
spring.datasource.username=
spring.jpa.properties.hibernate.default_schema=manual_loads
spring.datasource.hikari.schema=manual_loads
hibernate.temp.use_jdbc_metadata_defaults=false
spring.jpa.properties.hibernate.temp.use_jdbc_metadata_defaults=false
logging.level.org=TRACE
spring.jpa.hibernate.ddl-auto=none
spring.main.allow-bean-definition-overriding=true
spring.main.banner-mode=off
spring.profiles.active=dev
teiid.vdb-file=dwh.ddl
{code}
In logs we saw that Teeiid load all metadata from DB not only concrete schema
{code}
FE=> Sync
<=BE BindComplete [unnamed]
<=BE DataRow(len=2)
<=BE CommandStatus(SELECT 1)
<=BE ReadyForQuery(I)
simple execute, handler=org.postgresql.jdbc.PgStatement$StatementResultHandler@8301268, maxRows=0, fetchSize=0, flags=16
FE=> Bind(stmt=S_1,portal=null,$1=<'_xuotedocument'>,type=VARCHAR)
FE=> Execute(portal=null,limit=0)
FE=> Sync
<=BE BindComplete [unnamed]
<=BE DataRow(len=2)
<=BE CommandStatus(SELECT 1)
<=BE ReadyForQuery(I)
simple execute, handler=org.postgresql.jdbc.PgStatement$StatementResultHandler@3bbb53f6, maxRows=0, fetchSize=0, flags=16
FE=> Bind(stmt=S_1,portal=null,$1=<'_xuotelineitem'>,type=VARCHAR)
FE=> Execute(portal=null,limit=0)
FE=> Sync
<=BE BindComplete [unnamed]
<=BE DataRow(len=2)
<=BE CommandStatus(SELECT 1)
<=BE ReadyForQuery(I)
{code}
> Teiid imported all schemas from PG
> ----------------------------------
>
> Key: TEIID-5963
> URL: https://issues.redhat.com/browse/TEIID-5963
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 12.3.1
> Reporter: Renat Eskenin
> Assignee: Steven Hawkins
> Priority: Major
>
> When we started teiid spring boot app, we have long start time.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 11 months
[JBoss JIRA] (TEIID-5963) Teiid imported all schemas from PG
by Renat Eskenin (Jira)
Renat Eskenin created TEIID-5963:
------------------------------------
Summary: Teiid imported all schemas from PG
Key: TEIID-5963
URL: https://issues.redhat.com/browse/TEIID-5963
Project: Teiid
Issue Type: Bug
Components: JDBC Connector
Affects Versions: 12.3.1
Reporter: Renat Eskenin
Assignee: Steven Hawkins
When we started teiid spring boot app, we have long start time.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 11 months
[JBoss JIRA] (TEIID-5962) Teiid locks many threads when Salesforce is disconnected
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5962?page=com.atlassian.jira.plugi... ]
Steven Hawkins commented on TEIID-5962:
---------------------------------------
Looks like full set of resource adapter properties should be added to the docs page. I don't see the resource adapter timeout properties on http://teiid.github.io/teiid-documents/master/content/admin/Salesforce_Da... only the timeouts if directly using cxf.
They will auto-complete / be available in the cli for example - /subsystem=resource-adapters/resource-adapter=salesforce/connection-definitions=dsName/config-properties=propertyName
where propertyName will be requestTimeout or connectTimeout.
> Teiid locks many threads when Salesforce is disconnected
> --------------------------------------------------------
>
> Key: TEIID-5962
> URL: https://issues.redhat.com/browse/TEIID-5962
> Project: Teiid
> Issue Type: Bug
> Components: Salesforce Connector
> Affects Versions: 12.3.1
> Reporter: Renat Eskenin
> Assignee: Steven Hawkins
> Priority: Major
> Attachments: Снимок экрана от 2020-05-31 11-09-10.png
>
>
> We had two incidents in our experimental service with teiid spring boot app. When Salesforce is down to 20min and service with teiid trying to call SQL from Salesforce we have many threads in tomcat server (in spring boot app). Then when 200 threads is activated service do not reply to requests because is "max threads" in tomcat of service.
> Why teiid do not send response as "Salesforce is down - error" or connection timeout?
> Micro schema:
> HTTP Requests to REST api -> Teiid spring boot app -> {broken 20min}Salesforce
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 11 months
[JBoss JIRA] (TEIID-5962) Teiid locks many threads when Salesforce is disconnected
by Renat Eskenin (Jira)
[ https://issues.redhat.com/browse/TEIID-5962?page=com.atlassian.jira.plugi... ]
Renat Eskenin commented on TEIID-5962:
--------------------------------------
No, we haven't. Can you please describe this properties or give documentation?
> Teiid locks many threads when Salesforce is disconnected
> --------------------------------------------------------
>
> Key: TEIID-5962
> URL: https://issues.redhat.com/browse/TEIID-5962
> Project: Teiid
> Issue Type: Bug
> Components: Salesforce Connector
> Affects Versions: 12.3.1
> Reporter: Renat Eskenin
> Assignee: Steven Hawkins
> Priority: Major
> Attachments: Снимок экрана от 2020-05-31 11-09-10.png
>
>
> We had two incidents in our experimental service with teiid spring boot app. When Salesforce is down to 20min and service with teiid trying to call SQL from Salesforce we have many threads in tomcat server (in spring boot app). Then when 200 threads is activated service do not reply to requests because is "max threads" in tomcat of service.
> Why teiid do not send response as "Salesforce is down - error" or connection timeout?
> Micro schema:
> HTTP Requests to REST api -> Teiid spring boot app -> {broken 20min}Salesforce
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 11 months
[JBoss JIRA] (TEIID-5962) Teiid locks many threads when Salesforce is disconnected
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5962?page=com.atlassian.jira.plugi... ]
Steven Hawkins commented on TEIID-5962:
---------------------------------------
There is no default connection timeout. There is a property you can set on the resource adapter. Have you set the connect or the request timeouts?
> Teiid locks many threads when Salesforce is disconnected
> --------------------------------------------------------
>
> Key: TEIID-5962
> URL: https://issues.redhat.com/browse/TEIID-5962
> Project: Teiid
> Issue Type: Bug
> Components: Salesforce Connector
> Affects Versions: 12.3.1
> Reporter: Renat Eskenin
> Assignee: Steven Hawkins
> Priority: Major
> Attachments: Снимок экрана от 2020-05-31 11-09-10.png
>
>
> We had two incidents in our experimental service with teiid spring boot app. When Salesforce is down to 20min and service with teiid trying to call SQL from Salesforce we have many threads in tomcat server (in spring boot app). Then when 200 threads is activated service do not reply to requests because is "max threads" in tomcat of service.
> Why teiid do not send response as "Salesforce is down - error" or connection timeout?
> Micro schema:
> HTTP Requests to REST api -> Teiid spring boot app -> {broken 20min}Salesforce
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 11 months