[JBoss JIRA] (TEIIDDES-3029) Import salesforce via Teiid connection doesn't work
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3029?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-3029:
----------------------------------------
[~rareddy] debugged the request. It's the same request we always create to call getSchema() in the teiid connection importer.
{code}
{
"operation" => "get-schema",
"address" => [("subsystem" => "teiid")],
"vdb-name" => "importVDB",
"vdb-version" => 1,
"model-name" => "importVDBSrcModel"
}
{code}
The error is being thrown in ModelNode.readExternal() where the input char/byte arrays contains:
[r, e, s, u, l, t, s,
[114, 101, 115, 117, 108, 116, 115,
For some reason it's checking the first character of that array and getting a *S* and throws an Illegal arg exception.
> Import salesforce via Teiid connection doesn't work
> ---------------------------------------------------
>
> Key: TEIIDDES-3029
> URL: https://issues.jboss.org/browse/TEIIDDES-3029
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 11.0.1
> Environment: Fedora 24
> Reporter: Matej Kralik
> Priority: Blocker
> Attachments: schreenshot1.png
>
>
> When I wanted to import models from salesforce data source via Teiid connection importer, the Teiid importer shows me this error:
> {code:java}
> Error retrieving the Teiid DDL.
> Please check the logs for details...
> {code}
> In the error log is this event:
> java.io.IOException: java.util.concurrent.ExecutionException: Operation failed
> Stacktrace
> {code:java}
> org.teiid.adminapi.AdminComponentException: java.io.IOException: java.util.concurrent.ExecutionException: Operation failed
> at org.teiid.runtime.client.admin.v8.Admin8Factory$AdminImpl.getSchema(Admin8Factory.java:2076)
> at org.teiid.runtime.client.admin.ExecutionAdmin.getSchema(ExecutionAdmin.java:269)
> at org.teiid.designer.runtime.TeiidServer.getSchema(TeiidServer.java:800)
> at org.teiid.designer.runtime.importer.ImportManager.getSchema(ImportManager.java:258)
> at org.teiid.designer.teiidimporter.ui.wizard.TeiidImportManager.getDdl(TeiidImportManager.java:382)
> at org.teiid.designer.teiidimporter.ui.wizard.ShowDDLPage.setVisible(ShowDDLPage.java:337)
> at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1215)
> at org.eclipse.jface.wizard.WizardDialog.lambda$2(WizardDialog.java:1185)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1185)
> at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:876)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:419)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:618)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5219)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4553)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4143)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
> at org.eclipse.jface.window.Window.open(Window.java:794)
> at org.eclipse.ui.internal.handlers.WizardHandler$Import.executeHandler(WizardHandler.java:158)
> at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:290)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:282)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:264)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:494)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:488)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:353)
> at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:155)
> at org.eclipse.ui.internal.actions.CommandAction.run(CommandAction.java:165)
> at org.eclipse.ui.actions.ImportResourcesAction.run(ImportResourcesAction.java:99)
> at org.eclipse.ui.actions.BaseSelectionListenerAction.runWithEvent(BaseSelectionListenerAction.java:167)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565)
> at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5219)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4553)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4143)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
> Caused by: java.io.IOException: java.util.concurrent.ExecutionException: Operation failed
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:149)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:75)
> at org.teiid.runtime.client.admin.v8.Admin8Factory$AdminImpl.getSchema(Admin8Factory.java:2070)
> ... 70 more
> Caused by: java.util.concurrent.ExecutionException: Operation failed
> at org.jboss.threads.AsyncFutureTask.operationFailed(AsyncFutureTask.java:74)
> at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:268)
> at org.jboss.as.controller.client.impl.AbstractDelegatingAsyncFuture.get(AbstractDelegatingAsyncFuture.java:57)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147)
> ... 72 more
> Caused by: java.io.InvalidObjectException: Invalid type character 'S'
> at org.jboss.dmr.ModelNode.readExternal(ModelNode.java:1538)
> at org.jboss.dmr.ObjectModelValue.<init>(ObjectModelValue.java:62)
> at org.jboss.dmr.ModelNode.readExternal(ModelNode.java:1531)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient$1.handleRequest(AbstractModelControllerClient.java:196)
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:270)
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler.handleRequest(AbstractMessageHandler.java:235)
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:114)
> at org.jboss.as.protocol.mgmt.ManagementChannelReceiver$1.handleMessage(ManagementChannelReceiver.java:58)
> at org.jboss.as.protocol.mgmt.ManagementChannelReceiver.handleMessage(ManagementChannelReceiver.java:86)
> at org.jboss.remoting3.remote.RemoteConnectionChannel$5.run(RemoteConnectionChannel.java:452)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (TEIIDDES-2536) No connection to Teiid instance after starting DV from JBDS - refresh needed
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2536?page=com.atlassian.jira.plu... ]
Matus Makovy updated TEIIDDES-2536:
-----------------------------------
Affects Version/s: 11.0.1
> No connection to Teiid instance after starting DV from JBDS - refresh needed
> ----------------------------------------------------------------------------
>
> Key: TEIIDDES-2536
> URL: https://issues.jboss.org/browse/TEIIDDES-2536
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 9.0.2, 11.0.1
> Reporter: Matus Makovy
> Assignee: Barry LaFond
> Labels: release_notes, verified_jbdsis-8.0.4.CR2
> Fix For: 9.0.4, 9.2
>
> Attachments: Screen Shot 2015-05-20 at 9.40.55 AM.png, Screen Shot 2015-05-20 at 9.41.04 AM.png, Screen Shot 2015-09-29 at 13.50.18.png, running-server-not-available.png, server-contents-still-loading.png, server-started-connection-incomplete.png
>
>
> When you start DV server from JBDS there is no connection established to Teiid instance. You have to refresh server or Teiid Instance. Sometimes it is sufficient to expand particular server node in Servers view.
> I think this issue is releated to TEIIDDES-2512
> Screenshots attached
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (TEIIDDES-2536) No connection to Teiid instance after starting DV from JBDS - refresh needed
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2536?page=com.atlassian.jira.plu... ]
Matus Makovy reopened TEIIDDES-2536:
------------------------------------
This happens again in TD 11.0.1
> No connection to Teiid instance after starting DV from JBDS - refresh needed
> ----------------------------------------------------------------------------
>
> Key: TEIIDDES-2536
> URL: https://issues.jboss.org/browse/TEIIDDES-2536
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 9.0.2, 11.0.1
> Reporter: Matus Makovy
> Assignee: Barry LaFond
> Labels: release_notes, verified_jbdsis-8.0.4.CR2
> Fix For: 9.0.4, 9.2
>
> Attachments: Screen Shot 2015-05-20 at 9.40.55 AM.png, Screen Shot 2015-05-20 at 9.41.04 AM.png, Screen Shot 2015-09-29 at 13.50.18.png, running-server-not-available.png, server-contents-still-loading.png, server-started-connection-incomplete.png
>
>
> When you start DV server from JBDS there is no connection established to Teiid instance. You have to refresh server or Teiid Instance. Sometimes it is sufficient to expand particular server node in Servers view.
> I think this issue is releated to TEIIDDES-2512
> Screenshots attached
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (TEIIDDES-3033) Automatic add columns by using native SQL query
by SHI HONG CHIN (JIRA)
SHI HONG CHIN created TEIIDDES-3033:
---------------------------------------
Summary: Automatic add columns by using native SQL query
Key: TEIIDDES-3033
URL: https://issues.jboss.org/browse/TEIIDDES-3033
Project: Teiid Designer
Issue Type: Feature Request
Reporter: SHI HONG CHIN
Attachments: 01.jpg, 02.jpg, 03.jpg
I am still using Teiid Designer version 8.6.1.
Due to the need of using native SQL queries, sometimes I manually create a table, procedure, etc in Teiid Designer.
!01.jpg|thumbnail!
As you can see in the above screenshot, when creating a relational procedure which return a resultset, I have to manually add column to the result set. If I have many columns to be added, this is time consuming.
I hope that the developers of Teiid designer add a feature to allow me to use native SQL query to add columns to the procedure resultset. The datatype and length of the column should be set automatically based on SQL query result. For example, I can just input a native SQL query like "SELECT * FROM TABLEA WHERE COL1 = .......", the columns from the query result will be automatically added to the procedure resultset.
!02.jpg|thumbnail!
Same issue in creating relational table with native query. In teiid designer, if I want to create a relational table which use native query, I have to manually add the columns. So, I hope that the developers of Teiid designer add a feature to allow me to use native SQL query to add columns to the relational table.
Let me give you an example of software which allow me to add columns information by using SQL query. Take a look at the Jaspersoft Studio ( http://community.jaspersoft.com/project/jaspersoft-studio ). It is a software which allow us to design report layout to be used by Business Intelligence software developed by TIBCO.
!03.jpg|thumbnail!
As you can see, in Jaspersoft Studio, I just need to input a SQL query and then click on "Read Fields", the columns information will be automatically added to the report.
Developers of Teiid Designer can implement this feature by either one of the following methods:
1. In the "Native Query" tab of both "Create Relational Table" and "Create Relational Procedure" dialogues, add a button to run the query. After running the query, the columns information from the query result will be automatically added to the "COLUMNS" tab or result set of procedure.
2. In the "Columns" tab of "Create Relational Table" dialog and the "Result Set" tab of "Create Relational Procedure", add a button which will display another dialog for us to enter native query which will be run to add column information.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (TEIIDDES-3010) Add feature to provide adding After Triggers to materialized views/tables
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3010?page=com.atlassian.jira.plu... ]
Ramesh Reddy commented on TEIIDDES-3010:
----------------------------------------
So, when a user click on a view, this what they will see on the bottom? I did not quite understand the top portion of it, looked like whole separate wizard.
> Add feature to provide adding After Triggers to materialized views/tables
> -------------------------------------------------------------------------
>
> Key: TEIIDDES-3010
> URL: https://issues.jboss.org/browse/TEIIDDES-3010
> Project: Teiid Designer
> Issue Type: Enhancement
> Reporter: Steven Hawkins
> Assignee: Barry LaFond
> Priority: Blocker
> Fix For: 12.0
>
> Attachments: Sample Materialization Editor Page.bmml, Sample Materialization Editor Page.png, teditor-toolbar.png
>
>
> TEIID-4627 adds support for source level triggers to be called after CDC events.
> The triggers are similar to what is supported by views, but "INSTEAD OF" is not supported - just AFTER.
> CREATE TRIGGER name ON table AFTER (INSERT|UPDATE|DELETE) FOR EACH ROW statement
> Just like view triggers new/old/changing values can be referenced. Note that unlike view triggers, these must be named as an arbitrary number of them are supported per table (like other of our constructs they are scoped to the table, not to the schema).
> We may eventually want to support multiple event types for a single trigger and may need to support internal events as well.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (TEIIDDES-3030) inputMessage is garbled at TeiidWSProvider when JDV booting with Shift-jis encoding
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3030?page=com.atlassian.jira.plu... ]
Ted Jones commented on TEIIDDES-3030:
-------------------------------------
We are defaulting to UTF-8 in TeiidWSProvider. If we can determine the SOAP message encoding, we should definitely use that. Otherwise, we will need to add an "encoding" field to the WAR generator and use that.
> inputMessage is garbled at TeiidWSProvider when JDV booting with Shift-jis encoding
> -----------------------------------------------------------------------------------
>
> Key: TEIIDDES-3030
> URL: https://issues.jboss.org/browse/TEIIDDES-3030
> Project: Teiid Designer
> Issue Type: Bug
> Components: Web Services Support
> Affects Versions: 9.0.7
> Environment: JDV 6.2.4
> JBDS 8.1.0.GA
> Teiid Designer 9.0.6 (integration stack 8.0.6) and 9.0.7
> Reporter: Hiroki Daicho
> Assignee: Ted Jones
> Attachments: reproducer.zip
>
>
> When logging inputvalue by SYSADMIN.logmsg on Web service (created by teiid designer),
> the log message is garbled if the JDV booting with shift-jis encoding.
> 1. Generate War from VDB including webservice on Teiid Designer.
> 1-1. create procedure (the procedure logs input parameter by SYSADMIN.logmsg)
> 1-2. modeling -> create Web Service
> 1-3. create vdb includeing the web service
> 1-4. modeling -> Generate SOAP war
> 2. Deploy the vdb and war to JDV.
> 3. JDV boot with Shift-jis encoding.
> 4. call the webservice with testclient, the log will be garbled.
> I attached reproducer.zip.
> - testproject (JBDS project)
> - testclient (webservice client)
> - newvdb.war (generated web service)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (TEIIDDES-3010) Add feature to provide adding After Triggers to materialized views/tables
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3010?page=com.atlassian.jira.plu... ]
Steven Hawkins commented on TEIIDDES-3010:
------------------------------------------
Yes, that is heading in the right direction. And somehow having a more concise/specific display of the materialization properties can be added in as well.
> Add feature to provide adding After Triggers to materialized views/tables
> -------------------------------------------------------------------------
>
> Key: TEIIDDES-3010
> URL: https://issues.jboss.org/browse/TEIIDDES-3010
> Project: Teiid Designer
> Issue Type: Enhancement
> Reporter: Steven Hawkins
> Assignee: Barry LaFond
> Priority: Blocker
> Fix For: 12.0
>
> Attachments: Sample Materialization Editor Page.bmml, Sample Materialization Editor Page.png, teditor-toolbar.png
>
>
> TEIID-4627 adds support for source level triggers to be called after CDC events.
> The triggers are similar to what is supported by views, but "INSTEAD OF" is not supported - just AFTER.
> CREATE TRIGGER name ON table AFTER (INSERT|UPDATE|DELETE) FOR EACH ROW statement
> Just like view triggers new/old/changing values can be referenced. Note that unlike view triggers, these must be named as an arbitrary number of them are supported per table (like other of our constructs they are scoped to the table, not to the schema).
> We may eventually want to support multiple event types for a single trigger and may need to support internal events as well.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (TEIIDDES-2810) Import/Export Dynamic VDB utility doesn't transfer model descriptions
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2810?page=com.atlassian.jira.plu... ]
Matus Makovy closed TEIIDDES-2810.
----------------------------------
> Import/Export Dynamic VDB utility doesn't transfer model descriptions
> ---------------------------------------------------------------------
>
> Key: TEIIDDES-2810
> URL: https://issues.jboss.org/browse/TEIIDDES-2810
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs
> Affects Versions: 9.2
> Reporter: Debbie Steigner
> Assignee: Barry LaFond
> Labels: release_notes
> Fix For: 10.0, 9.0.7, 11.0.1
>
> Attachments: DynamicVdb.patch
>
>
> import a dynamic vdb in Teid designer, the vdb and related models are generated, however, the descriptions are not taken into account properly. We expect to see the description in the Teiid designer.
> Same goes when we export a Teiid vdb to a vdb xml: the descriptions are not generated as xml elements.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (TEIIDDES-2810) Import/Export Dynamic VDB utility doesn't transfer model descriptions
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2810?page=com.atlassian.jira.plu... ]
Matus Makovy updated TEIIDDES-2810:
-----------------------------------
Labels: release_notes (was: )
> Import/Export Dynamic VDB utility doesn't transfer model descriptions
> ---------------------------------------------------------------------
>
> Key: TEIIDDES-2810
> URL: https://issues.jboss.org/browse/TEIIDDES-2810
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs
> Affects Versions: 9.2
> Reporter: Debbie Steigner
> Assignee: Barry LaFond
> Labels: release_notes
> Fix For: 10.0, 9.0.7, 11.0.1
>
> Attachments: DynamicVdb.patch
>
>
> import a dynamic vdb in Teid designer, the vdb and related models are generated, however, the descriptions are not taken into account properly. We expect to see the description in the Teiid designer.
> Same goes when we export a Teiid vdb to a vdb xml: the descriptions are not generated as xml elements.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (TEIIDDES-2927) Connection to remote DV doesn't work
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2927?page=com.atlassian.jira.plu... ]
Matus Makovy commented on TEIIDDES-2927:
----------------------------------------
I was able to connect to teiid 8.12.8, I will retest later with Teiid 9.0.4. Lowering the priority to critical for now.
> Connection to remote DV doesn't work
> ------------------------------------
>
> Key: TEIIDDES-2927
> URL: https://issues.jboss.org/browse/TEIIDDES-2927
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 10.1
> Reporter: Bram Gadeyne
> Priority: Blocker
>
> Hi,
> I'm using teiiddesigner 10.1 and teiid server 9.0.4.
> I could connect to teiid in the past from the designer 10.1 (I think it was to 9.0.2 when I originally created the connection). I always see this error in the logs:
> java.lang.IllegalArgumentException: admin
> at org.teiid.core.util.ArgCheck.isNotNull(ArgCheck.java:302)
> at org.teiid.runtime.client.admin.ExecutionAdmin.<init>(ExecutionAdmin.java:124)
> at org.teiid.runtime.client.admin.ExecutionAdminFactory.createExecutionAdmin(ExecutionAdminFactory.java:53)
> at org.teiid.designer.runtime.registry.TeiidRuntimeRegistry.getExecutionAdmin(TeiidRuntimeRegistry.java:90)
> at org.teiid.designer.runtime.TeiidServer.connect(TeiidServer.java:243)
> at org.teiid.designer.runtime.TeiidServer.reconnect(TeiidServer.java:293)
> at org.teiid.designer.runtime.TeiidParentServerListener$1.tryConnecting(TeiidParentServerListener.java:259)
> at org.teiid.designer.runtime.TeiidParentServerListener$1.run(TeiidParentServerListener.java:197)
> at java.lang.Thread.run(Thread.java:745)
> And a second one later on:
> java.lang.IllegalArgumentException: admin
> at org.teiid.core.util.ArgCheck.isNotNull(ArgCheck.java:302)
> at org.teiid.runtime.client.admin.ExecutionAdmin.<init>(ExecutionAdmin.java:124)
> at org.teiid.runtime.client.admin.ExecutionAdminFactory.createExecutionAdmin(ExecutionAdminFactory.java:53)
> at org.teiid.designer.runtime.registry.TeiidRuntimeRegistry.getExecutionAdmin(TeiidRuntimeRegistry.java:90)
> at org.teiid.designer.runtime.TeiidServer.connect(TeiidServer.java:243)
> at org.teiid.designer.runtime.TeiidServer.reconnect(TeiidServer.java:293)
> at org.teiid.designer.runtime.ui.server.SetDefaultServerAction$1.run(SetDefaultServerAction.java:196)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator$2$1.run(UiBusyIndicator.java:206)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4155)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3772)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.executeRunnable(UiBusyIndicator.java:227)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.showWhileInternal(UiBusyIndicator.java:159)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.showWhile(UiBusyIndicator.java:116)
> at org.teiid.designer.runtime.ui.server.SetDefaultServerAction.run(SetDefaultServerAction.java:191)
> at org.teiid.designer.runtime.ui.server.SetDefaultServerAction.execute(SetDefaultServerAction.java:285)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:493)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:343)
> at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:330)
> at org.teiid.designer.ui.explorer.ModelExplorerResourceNavigator$6.linkActivated(ModelExplorerResourceNavigator.java:711)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleActivate(AbstractHyperlink.java:233)
> at org.eclipse.ui.forms.widgets.ImageHyperlink.handleActivate(ImageHyperlink.java:201)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleMouseUp(AbstractHyperlink.java:327)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.access$2(AbstractHyperlink.java:311)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink$4.handleEvent(AbstractHyperlink.java:125)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4362)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1113)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4180)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3769)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months