[JBoss JIRA] (TEIIDSB-143) SAP Gateway returns 406
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIIDSB-143?page=com.atlassian.jira.plugi... ]
Steven Hawkins commented on TEIIDSB-143:
----------------------------------------
The fix is down in Teiid - the header accept application/atom+xml causes the 406 with sap if it is the last value, so the order of the accept values was reversed. Will need to be picked up with Teiid 13 to be resolved here.
> SAP Gateway returns 406
> -----------------------
>
> Key: TEIIDSB-143
> URL: https://issues.jboss.org/browse/TEIIDSB-143
> Project: Teiid Spring Boot
> Issue Type: Bug
> Components: datasource
> Reporter: Steven Hawkins
> Priority: Major
> Fix For: 1.3.0
>
> Original Estimate: 2 hours, 30 minutes
> Time Spent: 2 hours
> Remaining Estimate: 30 minutes
>
> After the header fix TEIIDSB-134 for some reason SAP responds with a 406 - it doesn't like having multiple accept header values at least when used through our spring boot rest support. Just sending application/xml works as expected.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (TEIIDSB-143) SAP Gateway returns 406
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIIDSB-143?page=com.atlassian.jira.plugi... ]
Steven Hawkins reassigned TEIIDSB-143:
--------------------------------------
Assignee: Steven Hawkins
> SAP Gateway returns 406
> -----------------------
>
> Key: TEIIDSB-143
> URL: https://issues.jboss.org/browse/TEIIDSB-143
> Project: Teiid Spring Boot
> Issue Type: Bug
> Components: datasource
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 1.3.0
>
> Original Estimate: 2 hours, 30 minutes
> Time Spent: 2 hours
> Remaining Estimate: 30 minutes
>
> After the header fix TEIIDSB-134 for some reason SAP responds with a 406 - it doesn't like having multiple accept header values at least when used through our spring boot rest support. Just sending application/xml works as expected.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (TEIIDSB-143) SAP Gateway returns 406
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIIDSB-143?page=com.atlassian.jira.plugi... ]
Steven Hawkins updated TEIIDSB-143:
-----------------------------------
Original Estimate: 2 hours, 30 minutes
Remaining Estimate: 2 hours, 30 minutes
> SAP Gateway returns 406
> -----------------------
>
> Key: TEIIDSB-143
> URL: https://issues.jboss.org/browse/TEIIDSB-143
> Project: Teiid Spring Boot
> Issue Type: Bug
> Components: datasource
> Reporter: Steven Hawkins
> Priority: Major
> Fix For: 1.3.0
>
> Original Estimate: 2 hours, 30 minutes
> Remaining Estimate: 2 hours, 30 minutes
>
> After the header fix TEIIDSB-134 for some reason SAP responds with a 406 - it doesn't like having multiple accept header values at least when used through our spring boot rest support. Just sending application/xml works as expected.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (TEIIDSB-143) SAP Gateway returns 406
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIIDSB-143?focusedWorklogId=12448125&pag... ]
Steven Hawkins logged work on TEIIDSB-143:
------------------------------------------
Author: Steven Hawkins
Created on: 26/Nov/19 10:24 AM
Start Date: 26/Nov/19 10:24 AM
Worklog Time Spent: 2 hours
Issue Time Tracking
-------------------
Remaining Estimate: 30 minutes (was: 2 hours, 30 minutes)
Time Spent: 2 hours
Worklog Id: (was: 12448125)
> SAP Gateway returns 406
> -----------------------
>
> Key: TEIIDSB-143
> URL: https://issues.jboss.org/browse/TEIIDSB-143
> Project: Teiid Spring Boot
> Issue Type: Bug
> Components: datasource
> Reporter: Steven Hawkins
> Priority: Major
> Fix For: 1.3.0
>
> Original Estimate: 2 hours, 30 minutes
> Time Spent: 2 hours
> Remaining Estimate: 30 minutes
>
> After the header fix TEIIDSB-134 for some reason SAP responds with a 406 - it doesn't like having multiple accept header values at least when used through our spring boot rest support. Just sending application/xml works as expected.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (TEIID-5857) Remove the modelauditfields execution property
by Steven Hawkins (Jira)
Steven Hawkins created TEIID-5857:
-------------------------------------
Summary: Remove the modelauditfields execution property
Key: TEIID-5857
URL: https://issues.jboss.org/browse/TEIID-5857
Project: Teiid
Issue Type: Quality Risk
Components: Salesforce Connector
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 13.0
Quite a while ago we added the import property modelAuditFields so that the execution property was no longer needed. It should be removed for clarity.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (TEIID-5856) Teiid generate wrong request to salesforce
by Renat Eskenin (Jira)
[ https://issues.jboss.org/browse/TEIID-5856?page=com.atlassian.jira.plugin... ]
Renat Eskenin commented on TEIID-5856:
--------------------------------------
i'm sorry i used this ddl (xml is from logs generated vdb)
{code}
CREATE DATABASE db;
USE DATABASE db;
CREATE FOREIGN DATA WRAPPER salesforce;
CREATE FOREIGN DATA WRAPPER mysalesforce type salesforce OPTIONS (supportsOrderBy true);
CREATE SERVER salesforce FOREIGN DATA WRAPPER salesforce OPTIONS ("resource-name" 'salesforce');
CREATE SCHEMA sf SERVER salesforce;
IMPORT FROM SERVER salesforce INTO sf OPTIONS("importer.useFullSchemaName" 'false', "importer.NormalizeNames" 'false', "import.modelAuditFields" 'true', "import.importStatstics" 'true');
{code}
in SYS.tables i have
{code:json}
{
"Cardinality": -1,
"NameInSource": "Product_License__c",
"Name": "Product_License__c",
"UID": "tid:000005adccd6-9897fe32-00000545",
"Type": "Table",
"IsPhysical": true,
"SupportsUpdates": true,
"IsMaterialized": false,
"VDBName": "db",
"IsSystem": false,
"SchemaUID": "tid:000005adccd6-00000e53-00000000",
"SchemaName": "sf"
}
{code}
It is true information about dependencies? Why this way do not working?
This variant of solution working fine
{code:sql}
SELECT originalLicense.Id,originalLicense.Status__c,originalLicense.ReplacementLicenseID__c,originalLicense.LicenseId__c,originalLicense.vlic_Contract_Number__c,replacementLicense.LicenseId__c as replacementLicenseId ,replacementLicense.Id as replacementLicenseObjectId FROM Product_License__c originalLicense LEFT OUTER JOIN OPTION /*+ MAKEDEP */ Product_License__c Product_License__c replacementLicense ON originalLicense.ReplacementLicenseID__c = replacementLicense.Id where originalLicense.vlic_Contract_Number__c = :contractNumber
{code}
> Teiid generate wrong request to salesforce
> ------------------------------------------
>
> Key: TEIID-5856
> URL: https://issues.jboss.org/browse/TEIID-5856
> Project: Teiid
> Issue Type: Bug
> Components: Salesforce Connector
> Environment: spring-boot teiid salesforce-connector
> Reporter: Renat Eskenin
> Assignee: Steven Hawkins
> Priority: Major
>
> When i call request to salesforce teiid get very long wrong request and then OOM, because teiid request all data in salesforce object.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (TEIIDSB-144) Calling setTransactionIsolation on pg driver causes the connection to be closed
by Steven Hawkins (Jira)
Steven Hawkins created TEIIDSB-144:
--------------------------------------
Summary: Calling setTransactionIsolation on pg driver causes the connection to be closed
Key: TEIIDSB-144
URL: https://issues.jboss.org/browse/TEIIDSB-144
Project: Teiid Spring Boot
Issue Type: Bug
Components: datasource
Reporter: Steven Hawkins
Fix For: 1.3.0
An attempt to set the isolation level 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)
6 years, 4 months
[JBoss JIRA] (TEIIDSB-144) Calling setTransactionIsolation on pg driver causes the connection to be closed
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIIDSB-144?page=com.atlassian.jira.plugi... ]
Steven Hawkins updated TEIIDSB-144:
-----------------------------------
Description:
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}
was:
An attempt to set the isolation level 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}
> Calling setTransactionIsolation on pg driver causes the connection to be closed
> -------------------------------------------------------------------------------
>
> Key: TEIIDSB-144
> URL: https://issues.jboss.org/browse/TEIIDSB-144
> Project: Teiid Spring Boot
> Issue Type: Bug
> Components: datasource
> Reporter: Steven Hawkins
> Priority: Major
> Fix For: 1.3.0
>
>
> 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)
6 years, 4 months