June 2020 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIIDSB-204) Unable to build due to teiid wildfly connectors are not built as part of its core-release profile

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-204?page=com.atlassian.jira.plug... ] Steven Hawkins resolved TEIIDSB-204. ------------------------------------ Resolution: Done Marking as resolved. If needed we can backport the module move to a support branch and to further cleanup/align the dependencies (primarily make teiid use the same spring version as teiid sb). > Unable to build due to teiid wildfly connectors are not built as part of its core-release profile > ------------------------------------------------------------------------------------------------- > > Key: TEIIDSB-204 > URL: https://issues.redhat.com/browse/TEIIDSB-204 > Project: Teiid Spring Boot > Issue Type: Bug > Components: core > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 1.6.0 > > Time Spent: 5 hours > Remaining Estimate: 0 minutes > > issue on the di branch for teiid-spring-boot, https://github.com/teiid/teiid-spring-boot/blob/ca4325b98ea54266af8ee9c2a... > it references the teiid wildfly connectors > wont build because wildfly isn't built as part of teiid core-release profile -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5963) Teiid imported all schemas from PG

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5963?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5963: ---------------------------------- Fix Version/s: 15.0 Original Estimate: 3 hours Remaining Estimate: 3 hours Story Points: 0.5 Sprint: DV Sprint 64 So either we need to come up with lazy type info fetching at least for postgresql and/or add an option to disable using getTypeInfo altogether. That will be worked under this issue. > 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: 14.0 > Reporter: Renat Eskenin > Assignee: Steven Hawkins > Priority: Major > Fix For: 15.0 > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > > When we started teiid spring boot app, we have long start time. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[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 reopened TEIIDSB-205: --------------------------------- > 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 > Fix For: 1.5.0 > > > 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)

4 years, 6 months

1
0
0 / 0

[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 commented on TEIIDSB-205: ------------------------------------- Needing to add antlr:antlr due to transitive issues in hibernate. > 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 > Fix For: 1.5.0 > > > 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)

4 years, 6 months

1
0
0 / 0

[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: -------------------------------- Git Pull Request: https://github.com/teiid/teiid-spring-boot/pull/236, https://github.com/teiid/teiid-spring-boot/pull/240 (was: https://github.com/teiid/teiid-spring-boot/pull/236) > 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 > Fix For: 1.5.0 > > > 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)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-204) Unable to build due to teiid wildfly connectors are not built as part of its core-release profile

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-204?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIIDSB-204: ----------------------------------- Fix Version/s: 1.6.0 > Unable to build due to teiid wildfly connectors are not built as part of its core-release profile > ------------------------------------------------------------------------------------------------- > > Key: TEIIDSB-204 > URL: https://issues.redhat.com/browse/TEIIDSB-204 > Project: Teiid Spring Boot > Issue Type: Bug > Components: core > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 1.6.0 > > Time Spent: 5 hours > Remaining Estimate: 0 minutes > > issue on the di branch for teiid-spring-boot, https://github.com/teiid/teiid-spring-boot/blob/ca4325b98ea54266af8ee9c2a... > it references the teiid wildfly connectors > wont build because wildfly isn't built as part of teiid core-release profile -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-204) Unable to build due to teiid wildfly connectors are not built as part of its core-release profile

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-204?page=com.atlassian.jira.plug... ] Ramesh Reddy commented on TEIIDSB-204: -------------------------------------- Yes, we should get this upstream and then to the DI branch as currently soap is commented to make progress with the build. > Unable to build due to teiid wildfly connectors are not built as part of its core-release profile > ------------------------------------------------------------------------------------------------- > > Key: TEIIDSB-204 > URL: https://issues.redhat.com/browse/TEIIDSB-204 > Project: Teiid Spring Boot > Issue Type: Bug > Components: core > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Blocker > Time Spent: 5 hours > Remaining Estimate: 0 minutes > > issue on the di branch for teiid-spring-boot, https://github.com/teiid/teiid-spring-boot/blob/ca4325b98ea54266af8ee9c2a... > it references the teiid wildfly connectors > wont build because wildfly isn't built as part of teiid core-release profile -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-204) Unable to build due to teiid wildfly connectors are not built as part of its core-release profile

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-204?page=com.atlassian.jira.plug... ] Steven Hawkins commented on TEIIDSB-204: ---------------------------------------- [~rhn-engineering-vhalbert] do you want the change to the cxf module committed upstream or at all? > Unable to build due to teiid wildfly connectors are not built as part of its core-release profile > ------------------------------------------------------------------------------------------------- > > Key: TEIIDSB-204 > URL: https://issues.redhat.com/browse/TEIIDSB-204 > Project: Teiid Spring Boot > Issue Type: Bug > Components: core > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Blocker > Time Spent: 5 hours > Remaining Estimate: 0 minutes > > issue on the di branch for teiid-spring-boot, https://github.com/teiid/teiid-spring-boot/blob/ca4325b98ea54266af8ee9c2a... > it references the teiid wildfly connectors > wont build because wildfly isn't built as part of teiid core-release profile -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[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: --------------------------------------- > And I think that behavior need to improve. You can try to look at Netflix Hystrix as example of this logic. There are several take-aways here. 1. Teiid Spring Boot not using a connection pool with a resource that can consume a thread could result in too much resource consumption in a scenario like this. There is already captured as TEIIDSB-163 2. It is not clear from what you have shown above what threads exactly are being held. A thread dump would help clarify. As Ramesh is saying if it's something under the salesforce library it will take some investigation as to how/why to interrupt/cleanup that thread. The Teiid engine already has quite a bit of logic to make sure that it's threads are managed appropriately. 3. The main doc set should show the timeout related properties. I'll at least work #3 under this issue. For #2 if you can provide a thread dump that would be great. > 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)

4 years, 6 months

1
0
0 / 0

[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 commented on TEIID-5963: -------------------------------------- Yes we had 3100 types and service started 12min. > 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: 14.0 > 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)

4 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2020