[JBoss JIRA] (TEIIDDES-3169) Missing native tag in Teiid Importer
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3169?page=com.atlassian.jira.plu... ]
Matej Kralik updated TEIIDDES-3169:
-----------------------------------
Labels: release_notes (was: )
> Missing native tag in Teiid Importer
> ------------------------------------
>
> Key: TEIIDDES-3169
> URL: https://issues.jboss.org/browse/TEIIDDES-3169
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 11.1.1
> Reporter: Matej Kralik
> Priority: Critical
> Labels: release_notes
> Fix For: 11.1.2
>
> Attachments: VDBcontent.png, dataSource.png, teiid-import-edit-vdb-xml.png, translator.png
>
>
> Teiid importer doesn't add the NATIVE tag to VDB content.
> Same problem as Van described [here|https://issues.jboss.org/browse/TEIIDDES-3084?focusedCommentId=13417...].
> I use jdg7.1-remote-cache quick start from server.
> I have VDB and data source on the server, I choose this datasource (dataSource.png) and set translator to infinispan-hotrod (translator.png) but server shows error:
> {code:java}
> 15:22:00,121 WARN [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID50036 VDB importVDB.1 model "importVDBSrcModel" metadata failed to load. Reason:TEIID25011 There are three ways to import the metadata,
> 1) Define "importer.ProtoFilePath" to read from a local .proto file.
> 2) Define "importer.ProtobufName" property to define .proto file name, when reading the .proto file from the Infinispan Cache directly.
> 3) Define the schema using DDL, then use also the "NATIVE" metadata repository to convert DDL into .proto file
> {code}
> I noticed in the Advanced tab that NATIVE tag is missing. (VDBcontent.png)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years
[JBoss JIRA] (TEIIDDES-3169) Missing native tag in Teiid Importer
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3169?page=com.atlassian.jira.plu... ]
Matej Kralik closed TEIIDDES-3169.
----------------------------------
> Missing native tag in Teiid Importer
> ------------------------------------
>
> Key: TEIIDDES-3169
> URL: https://issues.jboss.org/browse/TEIIDDES-3169
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 11.1.1
> Reporter: Matej Kralik
> Priority: Critical
> Labels: release_notes
> Fix For: 11.1.2
>
> Attachments: VDBcontent.png, dataSource.png, teiid-import-edit-vdb-xml.png, translator.png
>
>
> Teiid importer doesn't add the NATIVE tag to VDB content.
> Same problem as Van described [here|https://issues.jboss.org/browse/TEIIDDES-3084?focusedCommentId=13417...].
> I use jdg7.1-remote-cache quick start from server.
> I have VDB and data source on the server, I choose this datasource (dataSource.png) and set translator to infinispan-hotrod (translator.png) but server shows error:
> {code:java}
> 15:22:00,121 WARN [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID50036 VDB importVDB.1 model "importVDBSrcModel" metadata failed to load. Reason:TEIID25011 There are three ways to import the metadata,
> 1) Define "importer.ProtoFilePath" to read from a local .proto file.
> 2) Define "importer.ProtobufName" property to define .proto file name, when reading the .proto file from the Infinispan Cache directly.
> 3) Define the schema using DDL, then use also the "NATIVE" metadata repository to convert DDL into .proto file
> {code}
> I noticed in the Advanced tab that NATIVE tag is missing. (VDBcontent.png)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years
[JBoss JIRA] (TEIIDDES-3192) NPE when infinispan-hotrod is not set in the server
by Matej Kralik (JIRA)
Matej Kralik created TEIIDDES-3192:
--------------------------------------
Summary: NPE when infinispan-hotrod is not set in the server
Key: TEIIDDES-3192
URL: https://issues.jboss.org/browse/TEIIDDES-3192
Project: Teiid Designer
Issue Type: Bug
Affects Versions: 11.1.2
Reporter: Matej Kralik
Priority: Critical
Attachments: creationJDG7model.mkv
When I don't have any server in the Teiid Designer or I have imported JDV server without JDG7 translator (infinispan-hotrod), NPE is thrown after creating JDG7 materialization wizard and JDG7 Source model is not generated. After when I add the translator to the server
{code:java}
./jboss-cli.sh --connect --file=../docs/teiid/datasources/infinispan-hotrod-7.1/add-infinispan-hotrod-translator.cli
{code}
and refresh server in the Teiid Designer, Teiid Designer import MXD for JDG and creation JDG7 source model works. I mentioned this behavior in the [TEIIDDES-3174|https://issues.jboss.org/browse/TEIIDDES-3174]
I have also uploaded video to the attachment. (creationJDG7model.mkv)
I understand why this happened. Teiid Designer doesn't have any information about JDG7 MXD. So in my point of view, Teiid Designer *should not allow the user to finish JDG7 creation wizard* and shows the user error or warning that JGD7(infinispan-hotrod) MXD is no in the Teiid Designer or server and the user has to add (infinispan-hotrod) translator to the server first.
NPE:
{code:java}
java.lang.NullPointerException
at org.teiid.designer.transformation.materialization.MaterializedModelManager.setInfinispanConnectionProperties(MaterializedModelManager.java:643)
at org.teiid.designer.transformation.materialization.MaterializedModelManager.execute(MaterializedModelManager.java:180)
at org.teiid.designer.transformation.ui.wizards.jdg.MaterializationWizard.execute(MaterializationWizard.java:199)
at org.teiid.designer.transformation.ui.wizards.jdg.MaterializationWizard.access$1(MaterializationWizard.java:193)
at org.teiid.designer.transformation.ui.wizards.jdg.MaterializationWizard$2.run(MaterializationWizard.java:165)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years
[JBoss JIRA] (TEIIDDES-3175) MED for JDG7 set wrong NAMESPACE and properties prefix
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3175?page=com.atlassian.jira.plu... ]
Matej Kralik closed TEIIDDES-3175.
----------------------------------
> MED for JDG7 set wrong NAMESPACE and properties prefix
> ------------------------------------------------------
>
> Key: TEIIDDES-3175
> URL: https://issues.jboss.org/browse/TEIIDDES-3175
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 11.1.1
> Reporter: Matej Kralik
> Assignee: Barry LaFond
> Priority: Critical
> Labels: release_notes
> Fix For: 11.1.2
>
>
> For workaround in this issue [TEIIDDES-3174|https://issues.jboss.org/browse/TEIIDDES-3174] I manually set MED (infinispan-hotrod) for JDG7 source model. When I create vdb as XML, xml file contains namespace _'http://www.teiid.org/translator/infinispan/2017' AS teiid_infinispan-hotrod_ but when I want to deploy it, on the server shows warning:
> {code:java}
> 13:07:54,108 WARN [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID50036 VDB BookMat.1 model "BookJDGSource" metadata failed to load. Reason:TEIID60017 Invalid prefix teiid_infinispan, teiid_ is reserved for Teiid use.: org.teiid.metadata.MetadataException: TEIID60017 Invalid prefix teiid_infinispan, teiid_ is reserved for Teiid use.
> {code}
> I also noticed that name of properties are *teiid_infinispan-hotrod* but should be *teiid_ispn*.
> Generated model in xml vdb:
> {code:java}
> SET NAMESPACE 'http://www.teiid.org/translator/infinispan/2017' AS teiid_infinispan-hotrod
> CREATE FOREIGN TABLE viewBooks (
> isbn string(255) NOT NULL,
> title string(255),
> publisher integer OPTIONS(FIXED_LENGTH 'TRUE'),
> publishyear integer OPTIONS(FIXED_LENGTH 'TRUE'),
> edition integer OPTIONS(FIXED_LENGTH 'TRUE'),
> type string(255),
> CONSTRAINT pk_book PRIMARY KEY(isbn) OPTIONS(NAMEINSOURCE 'BOOKS')
> ) OPTIONS(UPDATABLE 'TRUE', "teiid_infinispan-hotrod:CACHE" 'books_indexed');
> CREATE FOREIGN TABLE ST_viewBooks (
> isbn string(255) NOT NULL,
> title string(255),
> publisher integer OPTIONS(FIXED_LENGTH 'TRUE'),
> publishyear integer OPTIONS(FIXED_LENGTH 'TRUE'),
> edition integer OPTIONS(FIXED_LENGTH 'TRUE'),
> type string(255),
> CONSTRAINT pk_book PRIMARY KEY(isbn) OPTIONS(NAMEINSOURCE 'BOOKS')
> ) OPTIONS(UPDATABLE 'TRUE', "teiid_infinispan-hotrod:CACHE" 'books_indexed_st');
> {code}
> Right model (in my opinion):
> {code:java}
> SET NAMESPACE 'http://www.teiid.org/translator/infinispan/2017' AS teiid_ispn
> CREATE FOREIGN TABLE viewBooks (
> isbn string(255) NOT NULL,
> title string(255),
> publisher integer OPTIONS(FIXED_LENGTH 'TRUE'),
> publishyear integer OPTIONS(FIXED_LENGTH 'TRUE'),
> edition integer OPTIONS(FIXED_LENGTH 'TRUE'),
> type string(255),
> CONSTRAINT pk_book PRIMARY KEY(isbn) OPTIONS(NAMEINSOURCE 'BOOKS')
> ) OPTIONS(UPDATABLE 'TRUE', "teiid_ispn:CACHE" 'books_indexed');
> CREATE FOREIGN TABLE ST_viewBooks (
> isbn string(255) NOT NULL,
> title string(255),
> publisher integer OPTIONS(FIXED_LENGTH 'TRUE'),
> publishyear integer OPTIONS(FIXED_LENGTH 'TRUE'),
> edition integer OPTIONS(FIXED_LENGTH 'TRUE'),
> type string(255),
> CONSTRAINT pk_book PRIMARY KEY(isbn) OPTIONS(NAMEINSOURCE 'BOOKS')
> ) OPTIONS(UPDATABLE 'TRUE', "teiid_ispn:CACHE" 'books_indexed_st');
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years
[JBoss JIRA] (TEIIDDES-3174) Infinispan-hotrod MXD is not set after JDG materialization wizard
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3174?page=com.atlassian.jira.plu... ]
Matej Kralik updated TEIIDDES-3174:
-----------------------------------
Labels: release_notes (was: )
> Infinispan-hotrod MXD is not set after JDG materialization wizard
> -----------------------------------------------------------------
>
> Key: TEIIDDES-3174
> URL: https://issues.jboss.org/browse/TEIIDDES-3174
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 11.1.1
> Reporter: Matej Kralik
> Assignee: Barry LaFond
> Priority: Critical
> Labels: release_notes
> Fix For: 11.1.2
>
>
> When I went through JDG7 materialization creation I noticed that MED for JDG7 source model is not set automatically. So I don't see Primary cache name and staging cache name which I set in the 'Generate Materialized JDG Module' wizard.
> I must set MED for this model manually (Modeling -> Manage Model Extension Definition -> Add -> infinispan-hotrod).
> After that, I see infinispan-hotrod:CACHE which I defined in the wizard.
> Typ of infinispan-hotrod is *imported* so I must have set up a server *before*.
> In my point of view, the designer should set MED for JDG7 source model automatically.
> My idea: after finish wizard, the designer set infinispan-hotrod MED for this model. If infinispan-hotrod MED is not imported yet, the designer should show an error dialog that server is not defined yet and MED is not available.
> When I generate source model for JDG6.6, MED is set correctly (because MED is built-in).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years
[JBoss JIRA] (TEIIDDES-3174) Infinispan-hotrod MXD is not set after JDG materialization wizard
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3174?page=com.atlassian.jira.plu... ]
Matej Kralik closed TEIIDDES-3174.
----------------------------------
> Infinispan-hotrod MXD is not set after JDG materialization wizard
> -----------------------------------------------------------------
>
> Key: TEIIDDES-3174
> URL: https://issues.jboss.org/browse/TEIIDDES-3174
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 11.1.1
> Reporter: Matej Kralik
> Assignee: Barry LaFond
> Priority: Critical
> Labels: release_notes
> Fix For: 11.1.2
>
>
> When I went through JDG7 materialization creation I noticed that MED for JDG7 source model is not set automatically. So I don't see Primary cache name and staging cache name which I set in the 'Generate Materialized JDG Module' wizard.
> I must set MED for this model manually (Modeling -> Manage Model Extension Definition -> Add -> infinispan-hotrod).
> After that, I see infinispan-hotrod:CACHE which I defined in the wizard.
> Typ of infinispan-hotrod is *imported* so I must have set up a server *before*.
> In my point of view, the designer should set MED for JDG7 source model automatically.
> My idea: after finish wizard, the designer set infinispan-hotrod MED for this model. If infinispan-hotrod MED is not imported yet, the designer should show an error dialog that server is not defined yet and MED is not available.
> When I generate source model for JDG6.6, MED is set correctly (because MED is built-in).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years
[JBoss JIRA] (TEIIDDES-3175) MED for JDG7 set wrong NAMESPACE and properties prefix
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3175?page=com.atlassian.jira.plu... ]
Matej Kralik updated TEIIDDES-3175:
-----------------------------------
Labels: release_notes (was: )
> MED for JDG7 set wrong NAMESPACE and properties prefix
> ------------------------------------------------------
>
> Key: TEIIDDES-3175
> URL: https://issues.jboss.org/browse/TEIIDDES-3175
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 11.1.1
> Reporter: Matej Kralik
> Assignee: Barry LaFond
> Priority: Critical
> Labels: release_notes
> Fix For: 11.1.2
>
>
> For workaround in this issue [TEIIDDES-3174|https://issues.jboss.org/browse/TEIIDDES-3174] I manually set MED (infinispan-hotrod) for JDG7 source model. When I create vdb as XML, xml file contains namespace _'http://www.teiid.org/translator/infinispan/2017' AS teiid_infinispan-hotrod_ but when I want to deploy it, on the server shows warning:
> {code:java}
> 13:07:54,108 WARN [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID50036 VDB BookMat.1 model "BookJDGSource" metadata failed to load. Reason:TEIID60017 Invalid prefix teiid_infinispan, teiid_ is reserved for Teiid use.: org.teiid.metadata.MetadataException: TEIID60017 Invalid prefix teiid_infinispan, teiid_ is reserved for Teiid use.
> {code}
> I also noticed that name of properties are *teiid_infinispan-hotrod* but should be *teiid_ispn*.
> Generated model in xml vdb:
> {code:java}
> SET NAMESPACE 'http://www.teiid.org/translator/infinispan/2017' AS teiid_infinispan-hotrod
> CREATE FOREIGN TABLE viewBooks (
> isbn string(255) NOT NULL,
> title string(255),
> publisher integer OPTIONS(FIXED_LENGTH 'TRUE'),
> publishyear integer OPTIONS(FIXED_LENGTH 'TRUE'),
> edition integer OPTIONS(FIXED_LENGTH 'TRUE'),
> type string(255),
> CONSTRAINT pk_book PRIMARY KEY(isbn) OPTIONS(NAMEINSOURCE 'BOOKS')
> ) OPTIONS(UPDATABLE 'TRUE', "teiid_infinispan-hotrod:CACHE" 'books_indexed');
> CREATE FOREIGN TABLE ST_viewBooks (
> isbn string(255) NOT NULL,
> title string(255),
> publisher integer OPTIONS(FIXED_LENGTH 'TRUE'),
> publishyear integer OPTIONS(FIXED_LENGTH 'TRUE'),
> edition integer OPTIONS(FIXED_LENGTH 'TRUE'),
> type string(255),
> CONSTRAINT pk_book PRIMARY KEY(isbn) OPTIONS(NAMEINSOURCE 'BOOKS')
> ) OPTIONS(UPDATABLE 'TRUE', "teiid_infinispan-hotrod:CACHE" 'books_indexed_st');
> {code}
> Right model (in my opinion):
> {code:java}
> SET NAMESPACE 'http://www.teiid.org/translator/infinispan/2017' AS teiid_ispn
> CREATE FOREIGN TABLE viewBooks (
> isbn string(255) NOT NULL,
> title string(255),
> publisher integer OPTIONS(FIXED_LENGTH 'TRUE'),
> publishyear integer OPTIONS(FIXED_LENGTH 'TRUE'),
> edition integer OPTIONS(FIXED_LENGTH 'TRUE'),
> type string(255),
> CONSTRAINT pk_book PRIMARY KEY(isbn) OPTIONS(NAMEINSOURCE 'BOOKS')
> ) OPTIONS(UPDATABLE 'TRUE', "teiid_ispn:CACHE" 'books_indexed');
> CREATE FOREIGN TABLE ST_viewBooks (
> isbn string(255) NOT NULL,
> title string(255),
> publisher integer OPTIONS(FIXED_LENGTH 'TRUE'),
> publishyear integer OPTIONS(FIXED_LENGTH 'TRUE'),
> edition integer OPTIONS(FIXED_LENGTH 'TRUE'),
> type string(255),
> CONSTRAINT pk_book PRIMARY KEY(isbn) OPTIONS(NAMEINSOURCE 'BOOKS')
> ) OPTIONS(UPDATABLE 'TRUE', "teiid_ispn:CACHE" 'books_indexed_st');
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years
[JBoss JIRA] (TEIIDDES-3190) Problem with import from salesforce
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3190?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-3190:
----------------------------------------
[~mmajerni] [~shawkins] Teiid Designer currently only supports legacy salesforce API on it's importer. To add support for SF 34 or beyond, we'd need to add additional jars, probably add connection profile properties/checks to determine version, adjust the UI accordingly and add unit tests. My suggestion is to document this as a KI in Designer and direct users to use the Teiid Connection Import instead.
We could also add a URL check that could prevent users from continuing in the wizard if it's of the new format, but that doesn't seem like a blocker for this release.
> Problem with import from salesforce
> -----------------------------------
>
> Key: TEIIDDES-3190
> URL: https://issues.jboss.org/browse/TEIIDDES-3190
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 11.1.3
> Reporter: Mario Majernik
> Priority: Blocker
> Attachments: sales.png
>
>
> Import from salesforce do not work on TD 11.1.3 (neither with Teiid Connection import nor with Saleforce import)
> Last step: see sales.png image
> Server log:
> 4:25:34,589 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "importVDB-vdb.xml" (runtime-name: "importVDB-vdb.xml")
> 14:25:34,616 ERROR [stderr] (MSC service thread 1-2) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found
> 14:25:34,619 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (MSC service thread 1-2) TEIID40118 VDB importVDB.1 added to the repository
> 14:25:34,620 INFO [org.teiid.RUNTIME] (MSC service thread 1-2) TEIID50029 VDB importVDB.1 model "importVDBSrcModel" metadata is currently being loaded. Start Time: 4/24/18 2:25 PM
> 14:25:34,677 INFO [org.jboss.as.server] (management-handler-thread - 7) JBAS015859: Deployed "importVDB-vdb.xml" (runtime-name : "importVDB-vdb.xml")
> 14:25:36,253 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (teiid-async-threads - 4) IJ000604: Throwable while attempting to get a new connection: null: javax.resource.ResourceException: com.sforce.ws.ConnectionException: Failed to send request to https://www.salesforce.com/services/Soap/u/34.0
> at org.teiid.resource.adapter.salesforce.SalesforceConnectionImpl.login(SalesforceConnectionImpl.java:178)
> at org.teiid.resource.adapter.salesforce.SalesforceConnectionImpl.<init>(SalesforceConnectionImpl.java:88)
> at org.teiid.resource.adapter.salesforce.SalesForceManagedConnectionFactory$1.getConnection(SalesForceManagedConnectionFactory.java:98)
> at org.teiid.resource.adapter.salesforce.SalesForceManagedConnectionFactory$1.getConnection(SalesForceManagedConnectionFactory.java:93)
> at org.teiid.resource.spi.BasicManagedConnectionFactory.createManagedConnection(BasicManagedConnectionFactory.java:71) [teiid-api-8.12.11.6_4-redhat-64-12.jar:8.12.11.6_4-redhat-64-12]
> at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.createConnectionEventListener(SemaphoreArrayListManagedConnectionPool.java:858)
> at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.getConnection(SemaphoreArrayListManagedConnectionPool.java:413)
> at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getSimpleConnection(AbstractPool.java:457)
> at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getConnection(AbstractPool.java:429)
> at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:344)
> at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:317)
> at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:499)
> at org.teiid.resource.spi.WrappedConnectionFactory.getConnection(WrappedConnectionFactory.java:58) [teiid-api-8.12.11.6_4-redhat-64-12.jar:8.12.11.6_4-redhat-64-12]
> at org.teiid.translator.ExecutionFactory.getConnection(ExecutionFactory.java:181) [teiid-api-8.12.11.6_4-redhat-64-12.jar:8.12.11.6_4-redhat-64-12]
> at org.teiid.translator.ExecutionFactory.getConnection(ExecutionFactory.java:202) [teiid-api-8.12.11.6_4-redhat-64-12.jar:8.12.11.6_4-redhat-64-12]
> at org.teiid.query.metadata.NativeMetadataRepository.getMetadata(NativeMetadataRepository.java:72)
> at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:62)
> at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55)
> at org.teiid.jboss.VDBService$6.run(VDBService.java:395)
> at org.teiid.jboss.VDBService$7.run(VDBService.java:446)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_162]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_162]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_162]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> Caused by: com.sforce.ws.ConnectionException: Failed to send request to https://www.salesforce.com/services/Soap/u/34.0
> at com.sforce.ws.transport.SoapConnection.send(SoapConnection.java:121) [force-wsc-34.0.0.jar:]
> at com.sforce.soap.partner.PartnerConnection.login(PartnerConnection.java:1402) [force-partner-api-34.0.0.jar:]
> at org.teiid.resource.adapter.salesforce.TeiidPartnerConnection.login(TeiidPartnerConnection.java:54)
> at com.sforce.soap.partner.PartnerConnection.<init>(PartnerConnection.java:426) [force-partner-api-34.0.0.jar:]
> at org.teiid.resource.adapter.salesforce.TeiidPartnerConnection.<init>(TeiidPartnerConnection.java:46)
> at org.teiid.resource.adapter.salesforce.SalesforceConnectionImpl.login(SalesforceConnectionImpl.java:158)
> ... 23 more
> Caused by: java.net.SocketException: Connection reset
> at java.net.SocketInputStream.read(SocketInputStream.java:210) [rt.jar:1.8.0_162]
> at java.net.SocketInputStream.read(SocketInputStream.java:141) [rt.jar:1.8.0_162]
> at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) [jsse.jar:1.8.0_162]
> at sun.security.ssl.InputRecord.read(InputRecord.java:503) [jsse.jar:1.8.0_162]
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:983) [jsse.jar:1.8.0_162]
> at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:940) [jsse.jar:1.8.0_162]
> at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) [jsse.jar:1.8.0_162]
> at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) [rt.jar:1.8.0_162]
> at java.io.BufferedInputStream.read1(BufferedInputStream.java:286) [rt.jar:1.8.0_162]
> at java.io.BufferedInputStream.read(BufferedInputStream.java:345) [rt.jar:1.8.0_162]
> at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:735) [rt.jar:1.8.0_162]
> at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:678) [rt.jar:1.8.0_162]
> at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:706) [rt.jar:1.8.0_162]
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1587) [rt.jar:1.8.0_162]
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492) [rt.jar:1.8.0_162]
> at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:263) [rt.jar:1.8.0_162]
> at com.sforce.ws.transport.JdkHttpTransport.getContent(JdkHttpTransport.java:200) [force-wsc-34.0.0.jar:]
> at com.sforce.ws.transport.SoapConnection.send(SoapConnection.java:97) [force-wsc-34.0.0.jar:]
> ... 28 more
> 14:25:36,263 WARN [org.teiid.RUNTIME] (teiid-async-threads - 4) TEIID50036 VDB importVDB.1 model "importVDBSrcModel" metadata failed to load. Reason:TEIID31178 Could not obtain connection for schema importVDBSrcModel, but one is required for metadata load. : org.teiid.translator.TranslatorException: TEIID31178 Could not obtain connection for schema importVDBSrcModel, but one is required for metadata load.
> at org.teiid.query.metadata.NativeMetadataRepository.getMetadata(NativeMetadataRepository.java:76) [teiid-engine-8.12.11.6_4-redhat-64-12.jar:8.12.11.6_4-redhat-64-12]
> at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:62) [teiid-engine-8.12.11.6_4-redhat-64-12.jar:8.12.11.6_4-redhat-64-12]
> at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) [teiid-engine-8.12.11.6_4-redhat-64-12.jar:8.12.11.6_4-redhat-64-12]
> at org.teiid.jboss.VDBService$6.run(VDBService.java:395) [teiid-jboss-integration-8.12.11.6_4-redhat-64-12.jar:8.12.11.6_4-redhat-64-12]
> at org.teiid.jboss.VDBService$7.run(VDBService.java:446) [teiid-jboss-integration-8.12.11.6_4-redhat-64-12.jar:8.12.11.6_4-redhat-64-12]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_162]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_162]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_162]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> Caused by: org.teiid.translator.TranslatorException: TEIID60000 javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:/salesForceDS
> at org.teiid.translator.ExecutionFactory.getConnection(ExecutionFactory.java:183) [teiid-api-8.12.11.6_4-redhat-64-12.jar:8.12.11.6_4-redhat-64-12]
> at org.teiid.translator.ExecutionFactory.getConnection(ExecutionFactory.java:202) [teiid-api-8.12.11.6_4-redhat-64-12.jar:8.12.11.6_4-redhat-64-12]
> at org.teiid.query.metadata.NativeMetadataRepository.getMetadata(NativeMetadataRepository.java:72) [teiid-engine-8.12.11.6_4-redhat-64-12.jar:8.12.11.6_4-redhat-64-12]
> ... 8 more
> Caused by: javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:/salesForceDS
> at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:410) [ironjacamar-core-impl-1.0.39.Final-redhat-1.jar:1.0.39.Final-redhat-1]
> at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:317) [ironjacamar-core-impl-1.0.39.Final-redhat-1.jar:1.0.39.Final-redhat-1]
> at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:499) [ironjacamar-core-impl-1.0.39.Final-redhat-1.jar:1.0.39.Final-redhat-1]
> at org.teiid.resource.spi.WrappedConnectionFactory.getConnection(WrappedConnectionFactory.java:58) [teiid-api-8.12.11.6_4-redhat-64-12.jar:8.12.11.6_4-redhat-64-12]
> at org.teiid.translator.ExecutionFactory.getConnection(ExecutionFactory.java:181) [teiid-api-8.12.11.6_4-redhat-64-12.jar:8.12.11.6_4-redhat-64-12]
> ... 10 more
> Caused by: javax.resource.ResourceException: IJ000658: Unexpected throwable while trying to create a connection: null
> at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.getConnection(SemaphoreArrayListManagedConnectionPool.java:454) [ironjacamar-core-impl-1.0.39.Final-redhat-1.jar:1.0.39.Final-redhat-1]
> at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getSimpleConnection(AbstractPool.java:457) [ironjacamar-core-impl-1.0.39.Final-redhat-1.jar:1.0.39.Final-redhat-1]
> at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getConnection(AbstractPool.java:429) [ironjacamar-core-impl-1.0.39.Final-redhat-1.jar:1.0.39.Final-redhat-1]
> at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:344) [ironjacamar-core-impl-1.0.39.Final-redhat-1.jar:1.0.39.Final-redhat-1]
> ... 14 more
> Caused by: javax.resource.ResourceException: com.sforce.ws.ConnectionException: Failed to send request to https://www.salesforce.com/services/Soap/u/34.0
> at org.teiid.resource.adapter.salesforce.SalesforceConnectionImpl.login(SalesforceConnectionImpl.java:178)
> at org.teiid.resource.adapter.salesforce.SalesforceConnectionImpl.<init>(SalesforceConnectionImpl.java:88)
> at org.teiid.resource.adapter.salesforce.SalesForceManagedConnectionFactory$1.getConnection(SalesForceManagedConnectionFactory.java:98)
> at org.teiid.resource.adapter.salesforce.SalesForceManagedConnectionFactory$1.getConnection(SalesForceManagedConnectionFactory.java:93)
> at org.teiid.resource.spi.BasicManagedConnectionFactory.createManagedConnection(BasicManagedConnectionFactory.java:71) [teiid-api-8.12.11.6_4-redhat-64-12.jar:8.12.11.6_4-redhat-64-12]
> at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.createConnectionEventListener(SemaphoreArrayListManagedConnectionPool.java:858) [ironjacamar-core-impl-1.0.39.Final-redhat-1.jar:1.0.39.Final-redhat-1]
> at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.getConnection(SemaphoreArrayListManagedConnectionPool.java:413) [ironjacamar-core-impl-1.0.39.Final-redhat-1.jar:1.0.39.Final-redhat-1]
> ... 17 more
> Caused by: com.sforce.ws.ConnectionException: Failed to send request to https://www.salesforce.com/services/Soap/u/34.0
> at com.sforce.ws.transport.SoapConnection.send(SoapConnection.java:121)
> at com.sforce.soap.partner.PartnerConnection.login(PartnerConnection.java:1402)
> at org.teiid.resource.adapter.salesforce.TeiidPartnerConnection.login(TeiidPartnerConnection.java:54)
> at com.sforce.soap.partner.PartnerConnection.<init>(PartnerConnection.java:426)
> at org.teiid.resource.adapter.salesforce.TeiidPartnerConnection.<init>(TeiidPartnerConnection.java:46)
> at org.teiid.resource.adapter.salesforce.SalesforceConnectionImpl.login(SalesforceConnectionImpl.java:158)
> ... 23 more
> Caused by: java.net.SocketException: Connection reset
> at java.net.SocketInputStream.read(SocketInputStream.java:210) [rt.jar:1.8.0_162]
> at java.net.SocketInputStream.read(SocketInputStream.java:141) [rt.jar:1.8.0_162]
> at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) [jsse.jar:1.8.0_162]
> at sun.security.ssl.InputRecord.read(InputRecord.java:503) [jsse.jar:1.8.0_162]
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:983) [jsse.jar:1.8.0_162]
> at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:940) [jsse.jar:1.8.0_162]
> at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) [jsse.jar:1.8.0_162]
> at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) [rt.jar:1.8.0_162]
> at java.io.BufferedInputStream.read1(BufferedInputStream.java:286) [rt.jar:1.8.0_162]
> at java.io.BufferedInputStream.read(BufferedInputStream.java:345) [rt.jar:1.8.0_162]
> at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:735) [rt.jar:1.8.0_162]
> at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:678) [rt.jar:1.8.0_162]
> at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:706) [rt.jar:1.8.0_162]
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1587) [rt.jar:1.8.0_162]
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492) [rt.jar:1.8.0_162]
> at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:263) [rt.jar:1.8.0_162]
> at com.sforce.ws.transport.JdkHttpTransport.getContent(JdkHttpTransport.java:200)
> at com.sforce.ws.transport.SoapConnection.send(SoapConnection.java:97)
> ... 28 more
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years