[JBoss JIRA] (TEIIDSB-216) We get error with methadata in Salesforce request
by Renat Eskenin (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-216?page=com.atlassian.jira.plug... ]
Renat Eskenin edited comment on TEIIDSB-216 at 7/6/20 5:53 AM:
---------------------------------------------------------------
We get this error without timeouts. We used 45 API version in SF.
{code}
Caused by: org.teiid.jdbc.TeiidSQLException: TEIID30504 salesforce: Unrecognized header: {http://soap.sforce.com/2006/04/metadata}DebuggingInfo
at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:131)
at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:67)
at org.teiid.jdbc.StatementImpl.postReceiveResults(StatementImpl.java:786)
{code}
{code}
at org.teiid.salesforce.BaseSalesforceConnection.query(BaseSalesforceConnection.java:208)
at org.teiid.salesforce.BaseSalesforceConnection$$FastClassBySpringCGLIB$$9e945418.invoke(<generated>)
{code}
Why this header added to request? Can we just remove this header?
was (Author: i3draven):
We get this error without timeouts. We used 45 API version in SF.
{code}
Caused by: org.teiid.jdbc.TeiidSQLException: TEIID30504 salesforce: Unrecognized header: {http://soap.sforce.com/2006/04/metadata}DebuggingInfo
at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:131)
at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:67)
at org.teiid.jdbc.StatementImpl.postReceiveResults(StatementImpl.java:786)
{code}
Why this header added to request? Can we just remove this header?
> We get error with methadata in Salesforce request
> -------------------------------------------------
>
> Key: TEIIDSB-216
> URL: https://issues.redhat.com/browse/TEIIDSB-216
> Project: Teiid Spring Boot
> Issue Type: Bug
> Components: datasource
> Reporter: Renat Eskenin
> Priority: Major
>
> We get error from Teiid:
> {code}
> SQL state [50000]; error code [30504]; TEIID30504 salesforce: Unrecognized header: {http://soap.sforce.com/2006/04/metadata}DebuggingInfo; nested exception is org.teiid.jdbc.TeiidSQLException: TEIID30504 salesforce: Unrecognized header: {http://soap.sforce.com/2006/04/metadata}DebuggingInfo
> {code}
> As I think this error faired when we have connection timeout to Salesforce. In other time all works fine.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (TEIIDSB-216) We get error with methadata in Salesforce request
by Renat Eskenin (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-216?page=com.atlassian.jira.plug... ]
Renat Eskenin reopened TEIIDSB-216:
-----------------------------------
We get this error without timeouts. We used 45 API version in SF.
{code}
Caused by: org.teiid.jdbc.TeiidSQLException: TEIID30504 salesforce: Unrecognized header: {http://soap.sforce.com/2006/04/metadata}DebuggingInfo
at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:131)
at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:67)
at org.teiid.jdbc.StatementImpl.postReceiveResults(StatementImpl.java:786)
{code}
Why this header added to request? Can we just remove this header?
> We get error with methadata in Salesforce request
> -------------------------------------------------
>
> Key: TEIIDSB-216
> URL: https://issues.redhat.com/browse/TEIIDSB-216
> Project: Teiid Spring Boot
> Issue Type: Bug
> Components: datasource
> Reporter: Renat Eskenin
> Priority: Major
>
> We get error from Teiid:
> {code}
> SQL state [50000]; error code [30504]; TEIID30504 salesforce: Unrecognized header: {http://soap.sforce.com/2006/04/metadata}DebuggingInfo; nested exception is org.teiid.jdbc.TeiidSQLException: TEIID30504 salesforce: Unrecognized header: {http://soap.sforce.com/2006/04/metadata}DebuggingInfo
> {code}
> As I think this error faired when we have connection timeout to Salesforce. In other time all works fine.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (TEIIDSB-216) We get error with methadata in Salesforce request
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-216?page=com.atlassian.jira.plug... ]
Steven Hawkins resolved TEIIDSB-216.
------------------------------------
Resolution: Explained
I'll resolve this as explained. If you have additional information about when / why this occurs and/or if you want to see a feature where vdb deployment / metadata load is reattempted with Teiid Spring Boot, this can be reopened and updated.
> We get error with methadata in Salesforce request
> -------------------------------------------------
>
> Key: TEIIDSB-216
> URL: https://issues.redhat.com/browse/TEIIDSB-216
> Project: Teiid Spring Boot
> Issue Type: Bug
> Components: datasource
> Reporter: Renat Eskenin
> Priority: Major
>
> We get error from Teiid:
> {code}
> SQL state [50000]; error code [30504]; TEIID30504 salesforce: Unrecognized header: {http://soap.sforce.com/2006/04/metadata}DebuggingInfo; nested exception is org.teiid.jdbc.TeiidSQLException: TEIID30504 salesforce: Unrecognized header: {http://soap.sforce.com/2006/04/metadata}DebuggingInfo
> {code}
> As I think this error faired when we have connection timeout to Salesforce. In other time all works fine.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (TEIID-5981) Add content length to VirtualFileConnection.add
by Steven Hawkins (Jira)
Steven Hawkins created TEIID-5981:
-------------------------------------
Summary: Add content length to VirtualFileConnection.add
Key: TEIID-5981
URL: https://issues.redhat.com/browse/TEIID-5981
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 15.0
Using either an InputStreamFactory or another parameter the add method should have the stream length available or -1 if unknown. This will help with protocols that require the length which may otherwise have to materialize the stream in memory or disk to determine the length.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (TEIIDSB-195) Provide Connection properties Datasource
by Ramesh Reddy (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-195?page=com.atlassian.jira.plug... ]
Ramesh Reddy commented on TEIIDSB-195:
--------------------------------------
1) Added JDBC based configuration file to capture the properties
2) Added a way to reflectively look at the configuration files for any "spring-data-xxxx" project based on value defined on the "@ConnectionFactoryConfiguration" annotation and then generate the properties automatically from it.
3) one can enhance the properties by annotating the property using "@ConfigurationProperty" to define if it is required or not.
4) Also updated the Operator not use the JDBC driver versions directly but instead depend upon the "spring-data-xxxx" projects as dependencies which will in turn bring in the required dependencies.
> Provide Connection properties Datasource
> ----------------------------------------
>
> Key: TEIIDSB-195
> URL: https://issues.redhat.com/browse/TEIIDSB-195
> Project: Teiid Spring Boot
> Issue Type: Feature Request
> Components: datasource
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Priority: Major
> Fix For: 1.6.0
>
> Original Estimate: 2 days
> Time Spent: 4 days
> Remaining Estimate: 0 minutes
>
> When generating the connection factories JSON file, include the properties that are required for making a connection. This can then be used in design tools like VSCode or in Syndesis
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (TEIIDSB-195) Provide Connection properties Datasource
by Ramesh Reddy (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-195?focusedWorklogId=12451702&pa... ]
Ramesh Reddy logged work on TEIIDSB-195:
----------------------------------------
Author: Ramesh Reddy
Created on: 02/Jul/20 12:22 PM
Start Date: 02/Jul/20 12:22 PM
Worklog Time Spent: 4 days
Issue Time Tracking
-------------------
Remaining Estimate: 0 minutes (was: 2 days)
Time Spent: 4 days
Worklog Id: (was: 12451702)
> Provide Connection properties Datasource
> ----------------------------------------
>
> Key: TEIIDSB-195
> URL: https://issues.redhat.com/browse/TEIIDSB-195
> Project: Teiid Spring Boot
> Issue Type: Feature Request
> Components: datasource
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Priority: Major
> Fix For: 1.6.0
>
> Original Estimate: 2 days
> Time Spent: 4 days
> Remaining Estimate: 0 minutes
>
> When generating the connection factories JSON file, include the properties that are required for making a connection. This can then be used in design tools like VSCode or in Syndesis
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (TEIID-5979) how to create web service datasource for Google cloud APIs
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5979?page=com.atlassian.jira.plugi... ]
Steven Hawkins resolved TEIID-5979.
-----------------------------------
Resolution: Explained
> how to create web service datasource for Google cloud APIs
> ----------------------------------------------------------
>
> Key: TEIID-5979
> URL: https://issues.redhat.com/browse/TEIID-5979
> Project: Teiid
> Issue Type: Feature Request
> Components: Common
> Reporter: Nayan Bija
> Assignee: Steven Hawkins
> Priority: Major
>
> We need to create a web service data source to access google apis.
> I followed the steps mentioned in the below document
> [http://teiid.github.io/teiid-documents/master/content/admin/OAuth_Authent...]
>
> But getting below error after entering the Access Token URL.
> Could you please provide solution on it.
>
> Error logs.
> ===========
> WARNING: Default key managers cannot be initialized: Password must not be null
> java.security.UnrecoverableKeyException: Password must not be null
> at sun.security.provider.JavaKeyStore.engineGetKey(JavaKeyStore.java:124)
> at sun.security.provider.JavaKeyStore$JKS.engineGetKey(JavaKeyStore.java:55)
> at java.security.KeyStore.getKey(KeyStore.java:1011)
> at sun.security.ssl.SunX509KeyManagerImpl.<init>(SunX509KeyManagerImpl.java:133)
> at sun.security.ssl.KeyManagerFactoryImpl$SunX509.engineInit(KeyManagerFactoryImpl.java:70)
> at javax.net.ssl.KeyManagerFactory.init(KeyManagerFactory.java:256)
> at org.apache.cxf.configuration.jsse.SSLUtils.loadDefaultKeyManagers(SSLUtils.java:116)
> at org.apache.cxf.configuration.jsse.SSLUtils.getDefaultKeyStoreManagers(SSLUtils.java:89)
> at org.apache.cxf.transport.https.SSLUtils.getSSLContext(SSLUtils.java:75)
> at org.apache.cxf.transport.https.HttpsURLConnectionFactory.decorateWithTLS(HttpsURLConnectionFactory.java:144)
> at org.apache.cxf.transport.https.HttpsURLConnectionFactory.createConnection(HttpsURLConnectionFactory.java:101)
> at org.apache.cxf.transport.http.URLConnectionHTTPConduit.createConnection(URLConnectionHTTPConduit.java:121)
> at org.apache.cxf.transport.http.URLConnectionHTTPConduit.setupConnection(URLConnectionHTTPConduit.java:125)
> at org.apache.cxf.transport.http.asyncclient.AsyncHTTPConduit.setupConnection(AsyncHTTPConduit.java:190)
> at org.apache.cxf.transport.http.HTTPConduit.prepare(HTTPConduit.java:505)
> at org.apache.cxf.interceptor.MessageSenderInterceptor.handleMessage(MessageSenderInterceptor.java:47)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
> at org.apache.cxf.jaxrs.client.AbstractClient.doRunInterceptorChain(AbstractClient.java:701)
> at org.apache.cxf.jaxrs.client.WebClient.doChainedInvocation(WebClient.java:1086)
> at org.apache.cxf.jaxrs.client.WebClient.doInvoke(WebClient.java:932)
> at org.apache.cxf.jaxrs.client.WebClient.doInvoke(WebClient.java:901)
> at org.apache.cxf.jaxrs.client.WebClient.form(WebClient.java:434)
> at org.apache.cxf.rs.security.oauth2.client.OAuthClientUtils.getAccessToken(OAuthClientUtils.java:301)
> at org.apache.cxf.rs.security.oauth2.client.OAuthClientUtils.getAccessToken(OAuthClientUtils.java:225)
> at org.teiid.oauth.OAuthUtil.oauth20Flow(OAuthUtil.java:158)
> at org.teiid.oauth.OAuthUtil.main(OAuthUtil.java:76)
> at org.jboss.modules.Module.run(Module.java:352)
> at org.jboss.modules.Module.run(Module.java:320)
> at org.jboss.modules.Main.main(Main.java:593)
> Exception in thread "main" org.apache.cxf.rs.security.oauth2.provider.OAuthServiceException: server_error
> at org.apache.cxf.rs.security.oauth2.client.OAuthClientUtils.getAccessToken(OAuthClientUtils.java:323)
> at org.apache.cxf.rs.security.oauth2.client.OAuthClientUtils.getAccessToken(OAuthClientUtils.java:225)
> at org.teiid.oauth.OAuthUtil.oauth20Flow(OAuthUtil.java:158)
> at org.teiid.oauth.OAuthUtil.main(OAuthUtil.java:76)
> at org.jboss.modules.Module.run(Module.java:352)
> at org.jboss.modules.Module.run(Module.java:320)
> at org.jboss.modules.Main.main(Main.java:593)
> Press any key to continue . . .
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (TEIID-5979) how to create web service datasource for Google cloud APIs
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5979?page=com.atlassian.jira.plugi... ]
Steven Hawkins commented on TEIID-5979:
---------------------------------------
I can't find anything on this in terms of expected behavior, but you should be able to set system properties for the default keystore.
> how to create web service datasource for Google cloud APIs
> ----------------------------------------------------------
>
> Key: TEIID-5979
> URL: https://issues.redhat.com/browse/TEIID-5979
> Project: Teiid
> Issue Type: Feature Request
> Components: Common
> Reporter: Nayan Bija
> Assignee: Steven Hawkins
> Priority: Major
>
> We need to create a web service data source to access google apis.
> I followed the steps mentioned in the below document
> [http://teiid.github.io/teiid-documents/master/content/admin/OAuth_Authent...]
>
> But getting below error after entering the Access Token URL.
> Could you please provide solution on it.
>
> Error logs.
> ===========
> WARNING: Default key managers cannot be initialized: Password must not be null
> java.security.UnrecoverableKeyException: Password must not be null
> at sun.security.provider.JavaKeyStore.engineGetKey(JavaKeyStore.java:124)
> at sun.security.provider.JavaKeyStore$JKS.engineGetKey(JavaKeyStore.java:55)
> at java.security.KeyStore.getKey(KeyStore.java:1011)
> at sun.security.ssl.SunX509KeyManagerImpl.<init>(SunX509KeyManagerImpl.java:133)
> at sun.security.ssl.KeyManagerFactoryImpl$SunX509.engineInit(KeyManagerFactoryImpl.java:70)
> at javax.net.ssl.KeyManagerFactory.init(KeyManagerFactory.java:256)
> at org.apache.cxf.configuration.jsse.SSLUtils.loadDefaultKeyManagers(SSLUtils.java:116)
> at org.apache.cxf.configuration.jsse.SSLUtils.getDefaultKeyStoreManagers(SSLUtils.java:89)
> at org.apache.cxf.transport.https.SSLUtils.getSSLContext(SSLUtils.java:75)
> at org.apache.cxf.transport.https.HttpsURLConnectionFactory.decorateWithTLS(HttpsURLConnectionFactory.java:144)
> at org.apache.cxf.transport.https.HttpsURLConnectionFactory.createConnection(HttpsURLConnectionFactory.java:101)
> at org.apache.cxf.transport.http.URLConnectionHTTPConduit.createConnection(URLConnectionHTTPConduit.java:121)
> at org.apache.cxf.transport.http.URLConnectionHTTPConduit.setupConnection(URLConnectionHTTPConduit.java:125)
> at org.apache.cxf.transport.http.asyncclient.AsyncHTTPConduit.setupConnection(AsyncHTTPConduit.java:190)
> at org.apache.cxf.transport.http.HTTPConduit.prepare(HTTPConduit.java:505)
> at org.apache.cxf.interceptor.MessageSenderInterceptor.handleMessage(MessageSenderInterceptor.java:47)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
> at org.apache.cxf.jaxrs.client.AbstractClient.doRunInterceptorChain(AbstractClient.java:701)
> at org.apache.cxf.jaxrs.client.WebClient.doChainedInvocation(WebClient.java:1086)
> at org.apache.cxf.jaxrs.client.WebClient.doInvoke(WebClient.java:932)
> at org.apache.cxf.jaxrs.client.WebClient.doInvoke(WebClient.java:901)
> at org.apache.cxf.jaxrs.client.WebClient.form(WebClient.java:434)
> at org.apache.cxf.rs.security.oauth2.client.OAuthClientUtils.getAccessToken(OAuthClientUtils.java:301)
> at org.apache.cxf.rs.security.oauth2.client.OAuthClientUtils.getAccessToken(OAuthClientUtils.java:225)
> at org.teiid.oauth.OAuthUtil.oauth20Flow(OAuthUtil.java:158)
> at org.teiid.oauth.OAuthUtil.main(OAuthUtil.java:76)
> at org.jboss.modules.Module.run(Module.java:352)
> at org.jboss.modules.Module.run(Module.java:320)
> at org.jboss.modules.Main.main(Main.java:593)
> Exception in thread "main" org.apache.cxf.rs.security.oauth2.provider.OAuthServiceException: server_error
> at org.apache.cxf.rs.security.oauth2.client.OAuthClientUtils.getAccessToken(OAuthClientUtils.java:323)
> at org.apache.cxf.rs.security.oauth2.client.OAuthClientUtils.getAccessToken(OAuthClientUtils.java:225)
> at org.teiid.oauth.OAuthUtil.oauth20Flow(OAuthUtil.java:158)
> at org.teiid.oauth.OAuthUtil.main(OAuthUtil.java:76)
> at org.jboss.modules.Module.run(Module.java:352)
> at org.jboss.modules.Module.run(Module.java:320)
> at org.jboss.modules.Main.main(Main.java:593)
> Press any key to continue . . .
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months