[JBoss JIRA] (TEIID-5878) Support loading the protobuf file from the classpath
by Ramesh Reddy (Jira)
[ https://issues.redhat.com/browse/TEIID-5878?focusedWorklogId=12449914&pag... ]
Ramesh Reddy logged work on TEIID-5878:
---------------------------------------
Author: Ramesh Reddy
Created on: 17/Jan/20 12:49 PM
Start Date: 17/Jan/20 12:49 PM
Worklog Time Spent: 1 hour
Issue Time Tracking
-------------------
Remaining Estimate: 0 minutes
Time Spent: 1 hour
Worklog Id: (was: 12449914)
> Support loading the protobuf file from the classpath
> ----------------------------------------------------
>
> Key: TEIID-5878
> URL: https://issues.redhat.com/browse/TEIID-5878
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Reporter: Steven Hawkins
> Assignee: Ramesh Reddy
> Priority: Major
> Fix For: 13.0.2
>
> Time Spent: 1 hour
> Remaining Estimate: 0 minutes
>
> Providing a protobuf file should support loading from the classpath as well - currently it expects just a file system path.
> This will allow for inclusion of protobuf files in Teiid Spring Boot fat jars.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 11 months
[JBoss JIRA] (TEIIDSB-158) Salesforce connection factory uses a single connection
by Ramesh Reddy (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-158?focusedWorklogId=12449913&pa... ]
Ramesh Reddy logged work on TEIIDSB-158:
----------------------------------------
Author: Ramesh Reddy
Created on: 17/Jan/20 12:49 PM
Start Date: 17/Jan/20 12:49 PM
Worklog Time Spent: 1 hour
Issue Time Tracking
-------------------
Remaining Estimate: 0 minutes
Time Spent: 1 hour
Worklog Id: (was: 12449913)
> Salesforce connection factory uses a single connection
> ------------------------------------------------------
>
> Key: TEIIDSB-158
> URL: https://issues.redhat.com/browse/TEIIDSB-158
> Project: Teiid Spring Boot
> Issue Type: Bug
> Components: datasource
> Reporter: Steven Hawkins
> Assignee: Ramesh Reddy
> Priority: Major
> Fix For: 1.4.0, 1.3.1
>
> Time Spent: 1 hour
> Remaining Estimate: 0 minutes
>
> The current salesforce connection factory creates just a single connection. However the connection object is not thread-safe - setting query options, etc.
> Also if and when credential delegation is turned on we'll need separate connections as well so that everything is not run over a single session.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 11 months
[JBoss JIRA] (TEIIDSB-159) Test errors
by Steven Hawkins (Jira)
Steven Hawkins created TEIIDSB-159:
--------------------------------------
Summary: Test errors
Key: TEIIDSB-159
URL: https://issues.redhat.com/browse/TEIIDSB-159
Project: Teiid Spring Boot
Issue Type: Bug
Components: core
Reporter: Steven Hawkins
Fix For: 1.4.0, 1.3.1
The Teiid spring boot tests are commonly erroring out in travis. It usually is reported as Failed To Load Application Context - but the underlying problem differs. Here: https://api.travis-ci.org/v3/job/638096554/log.txt the issue is likely that tests are executing concurrently that reference the same vdb. The current NioVirtualFile logic for Teiid expects only one mount for a given zip. If you open another, then the previous is closed.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 11 months
[JBoss JIRA] (TEIIDSB-144) Calling setTransactionIsolation on pg driver causes the connection to be closed
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-144?page=com.atlassian.jira.plug... ]
Steven Hawkins resolved TEIIDSB-144.
------------------------------------
Resolution: Done
Added the reflective workaround as a side effect of loading the teiid auto configuration.
> Calling setTransactionIsolation on pg driver causes the connection to be closed
> -------------------------------------------------------------------------------
>
> Key: TEIIDSB-144
> URL: https://issues.redhat.com/browse/TEIIDSB-144
> Project: Teiid Spring Boot
> Issue Type: Bug
> Components: datasource
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 1.4.0, 1.3.1
>
> Original Estimate: 4 hours
> Time Spent: 4 hours, 30 minutes
> Remaining Estimate: 0 minutes
>
> An attempt to set the isolation level on pg 42.2.8 resulted in an exception SQLSTATE 0a000 - unsupported - which causes the connection pool to mark the connection as broken:
> {code}
> 2019-11-25 23:07:50.125 WARN 43993 --- [ProcessorQueue6] com.zaxxer.hikari.pool.ProxyConnection : HikariPool-1 - Connection org.postgresql.jdbc.PgConnection@2ffebc7e marked as broken because of SQLSTATE(0A000), ErrorCode(0)
> org.postgresql.util.PSQLException:
> at org.postgresql.jdbc.PgConnection.setTransactionIsolation(PgConnection.java:851) ~[postgresql-42.2.8.jar:42.2.8]
> at com.zaxxer.hikari.pool.ProxyConnection.setTransactionIsolation(ProxyConnection.java:407) ~[HikariCP-3.2.0.jar:na]
> at com.zaxxer.hikari.pool.HikariProxyConnection.setTransactionIsolation(HikariProxyConnection.java) ~[HikariCP-3.2.0.jar:na]
> at org.teiid.translator.jdbc.JDBCBaseExecution.<init>(JDBCBaseExecution.java:72) ~[translator-jdbc-12.3.0.jar:12.3.0]
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 11 months
[JBoss JIRA] (TEIIDSB-158) Salesforce connection factory uses a single connection
by Steven Hawkins (Jira)
Steven Hawkins created TEIIDSB-158:
--------------------------------------
Summary: Salesforce connection factory uses a single connection
Key: TEIIDSB-158
URL: https://issues.redhat.com/browse/TEIIDSB-158
Project: Teiid Spring Boot
Issue Type: Bug
Components: datasource
Reporter: Steven Hawkins
Fix For: 1.4.0, 1.3.1
The current salesforce connection factory creates just a single connection. However the connection object is not thread-safe - setting query options, etc.
Also if and when credential delegation is turned on we'll need separate connections as well so that everything is not run over a single session.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 11 months
[JBoss JIRA] (TEIIDSB-144) Calling setTransactionIsolation on pg driver causes the connection to be closed
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-144?page=com.atlassian.jira.plug... ]
Steven Hawkins commented on TEIIDSB-144:
----------------------------------------
His hack does not need to obtain a connection as the field is static. I've put in a pr to add something similar. However if there are additional error codes we'll need to expand this. Also it affects all datasources, not just pg. It will be good to eventually have the a better solution.
> Calling setTransactionIsolation on pg driver causes the connection to be closed
> -------------------------------------------------------------------------------
>
> Key: TEIIDSB-144
> URL: https://issues.redhat.com/browse/TEIIDSB-144
> Project: Teiid Spring Boot
> Issue Type: Bug
> Components: datasource
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 1.4.0, 1.3.1
>
> Original Estimate: 4 hours
> Time Spent: 2 hours
> Remaining Estimate: 2 hours
>
> An attempt to set the isolation level on pg 42.2.8 resulted in an exception SQLSTATE 0a000 - unsupported - which causes the connection pool to mark the connection as broken:
> {code}
> 2019-11-25 23:07:50.125 WARN 43993 --- [ProcessorQueue6] com.zaxxer.hikari.pool.ProxyConnection : HikariPool-1 - Connection org.postgresql.jdbc.PgConnection@2ffebc7e marked as broken because of SQLSTATE(0A000), ErrorCode(0)
> org.postgresql.util.PSQLException:
> at org.postgresql.jdbc.PgConnection.setTransactionIsolation(PgConnection.java:851) ~[postgresql-42.2.8.jar:42.2.8]
> at com.zaxxer.hikari.pool.ProxyConnection.setTransactionIsolation(ProxyConnection.java:407) ~[HikariCP-3.2.0.jar:na]
> at com.zaxxer.hikari.pool.HikariProxyConnection.setTransactionIsolation(HikariProxyConnection.java) ~[HikariCP-3.2.0.jar:na]
> at org.teiid.translator.jdbc.JDBCBaseExecution.<init>(JDBCBaseExecution.java:72) ~[translator-jdbc-12.3.0.jar:12.3.0]
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 11 months
[JBoss JIRA] (TEIIDSB-144) Calling setTransactionIsolation on pg driver causes the connection to be closed
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-144?focusedWorklogId=12449900&pa... ]
Steven Hawkins logged work on TEIIDSB-144:
------------------------------------------
Author: Steven Hawkins
Created on: 16/Jan/20 10:00 AM
Start Date: 16/Jan/20 10:00 AM
Worklog Time Spent: 2 hours, 30 minutes
Issue Time Tracking
-------------------
Remaining Estimate: 0 minutes (was: 2 hours)
Time Spent: 4 hours, 30 minutes (was: 2 hours)
Worklog Id: (was: 12449900)
> Calling setTransactionIsolation on pg driver causes the connection to be closed
> -------------------------------------------------------------------------------
>
> Key: TEIIDSB-144
> URL: https://issues.redhat.com/browse/TEIIDSB-144
> Project: Teiid Spring Boot
> Issue Type: Bug
> Components: datasource
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 1.4.0, 1.3.1
>
> Original Estimate: 4 hours
> Time Spent: 4 hours, 30 minutes
> Remaining Estimate: 0 minutes
>
> An attempt to set the isolation level on pg 42.2.8 resulted in an exception SQLSTATE 0a000 - unsupported - which causes the connection pool to mark the connection as broken:
> {code}
> 2019-11-25 23:07:50.125 WARN 43993 --- [ProcessorQueue6] com.zaxxer.hikari.pool.ProxyConnection : HikariPool-1 - Connection org.postgresql.jdbc.PgConnection@2ffebc7e marked as broken because of SQLSTATE(0A000), ErrorCode(0)
> org.postgresql.util.PSQLException:
> at org.postgresql.jdbc.PgConnection.setTransactionIsolation(PgConnection.java:851) ~[postgresql-42.2.8.jar:42.2.8]
> at com.zaxxer.hikari.pool.ProxyConnection.setTransactionIsolation(ProxyConnection.java:407) ~[HikariCP-3.2.0.jar:na]
> at com.zaxxer.hikari.pool.HikariProxyConnection.setTransactionIsolation(HikariProxyConnection.java) ~[HikariCP-3.2.0.jar:na]
> at org.teiid.translator.jdbc.JDBCBaseExecution.<init>(JDBCBaseExecution.java:72) ~[translator-jdbc-12.3.0.jar:12.3.0]
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 11 months
[JBoss JIRA] (TEIIDSB-144) Calling setTransactionIsolation on pg driver causes the connection to be closed
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-144?page=com.atlassian.jira.plug... ]
Work on TEIIDSB-144 started by Steven Hawkins.
----------------------------------------------
> Calling setTransactionIsolation on pg driver causes the connection to be closed
> -------------------------------------------------------------------------------
>
> Key: TEIIDSB-144
> URL: https://issues.redhat.com/browse/TEIIDSB-144
> Project: Teiid Spring Boot
> Issue Type: Bug
> Components: datasource
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 1.4.0, 1.3.1
>
> Original Estimate: 4 hours
> Time Spent: 2 hours
> Remaining Estimate: 2 hours
>
> An attempt to set the isolation level on pg 42.2.8 resulted in an exception SQLSTATE 0a000 - unsupported - which causes the connection pool to mark the connection as broken:
> {code}
> 2019-11-25 23:07:50.125 WARN 43993 --- [ProcessorQueue6] com.zaxxer.hikari.pool.ProxyConnection : HikariPool-1 - Connection org.postgresql.jdbc.PgConnection@2ffebc7e marked as broken because of SQLSTATE(0A000), ErrorCode(0)
> org.postgresql.util.PSQLException:
> at org.postgresql.jdbc.PgConnection.setTransactionIsolation(PgConnection.java:851) ~[postgresql-42.2.8.jar:42.2.8]
> at com.zaxxer.hikari.pool.ProxyConnection.setTransactionIsolation(ProxyConnection.java:407) ~[HikariCP-3.2.0.jar:na]
> at com.zaxxer.hikari.pool.HikariProxyConnection.setTransactionIsolation(HikariProxyConnection.java) ~[HikariCP-3.2.0.jar:na]
> at org.teiid.translator.jdbc.JDBCBaseExecution.<init>(JDBCBaseExecution.java:72) ~[translator-jdbc-12.3.0.jar:12.3.0]
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 11 months