[JBoss JIRA] (TEIIDDES-2002) Got errors when generate Rest wars
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2002?page=com.atlassian.jira.plu... ]
Ted Jones reassigned TEIIDDES-2002:
-----------------------------------
Assignee: Ted Jones
> Got errors when generate Rest wars
> ----------------------------------
>
> Key: TEIIDDES-2002
> URL: https://issues.jboss.org/browse/TEIIDDES-2002
> Project: Teiid Designer
> Issue Type: Bug
> Components: Web Services Support
> Affects Versions: 8.3
> Environment: Fedora 17, jboss EAP 6.1 with Teiid 8.4, eclipse 4.3.0 with Teiid Disigner 8.3
> Reporter: Gang Li
> Assignee: Ted Jones
>
> Hello,
> I'm trying to use teiid designer to develop a virtual procedure in a vdb, and try to deploy it as a REST war file to supply REST services. All view model and vdbs validation is passed. But when i try to generate the war file from vdb, i got two error logs in error log console:
> java.lang.NullPointerException
> at java.util.Hashtable.put(Hashtable.java:542)
> at org.teiid.designer.runtime.ui.wizards.webservices.RestWarDataserviceModel.getProperties(RestWarDataserviceModel.java:371)
> at org.teiid.designer.runtime.ui.wizards.webservices.RestWarDeploymentInfoDialog.execute(RestWarDeploymentInfoDialog.java:202)
> at org.teiid.designer.runtime.ui.wizards.webservices.RestWarDeploymentInfoDialog$1.run(RestWarDeploymentInfoDialog.java:165)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372)
> at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507)
> at org.teiid.designer.runtime.ui.wizards.webservices.RestWarDeploymentInfoDialog.okPressed(RestWarDeploymentInfoDialog.java:174)
> at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:476)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:628)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:826)
> at org.eclipse.jface.window.Window.open(Window.java:802)
> at org.teiid.designer.runtime.ui.wizards.webservices.RestWarDeploymentInfoDialog.open(RestWarDeploymentInfoDialog.java:186)
> at org.teiid.designer.runtime.ui.actions.GenerateRestWarAction.run(GenerateRestWarAction.java:147)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:499)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> and
> java.lang.IllegalArgumentException: Argument cannot be null
> at org.eclipse.swt.SWT.error(SWT.java:4378)
> at org.eclipse.swt.SWT.error(SWT.java:4312)
> at org.eclipse.swt.SWT.error(SWT.java:4283)
> at org.eclipse.swt.widgets.Widget.error(Widget.java:481)
> at org.eclipse.swt.widgets.Text.setText(Text.java:2426)
> at org.teiid.designer.runtime.ui.wizards.webservices.RestWarDeploymentInfoPanel.loadData(RestWarDeploymentInfoPanel.java:143)
> at org.teiid.designer.runtime.ui.wizards.webservices.RestWarDeploymentInfoDialog.loadDefault(RestWarDeploymentInfoDialog.java:250)
> at org.teiid.designer.runtime.ui.wizards.webservices.RestWarDeploymentInfoDialog.createButtonsForButtonBar(RestWarDeploymentInfoDialog.java:148)
> at org.eclipse.jface.dialogs.Dialog.createButtonBar(Dialog.java:676)
> at org.eclipse.jface.dialogs.TrayDialog.createButtonBar(TrayDialog.java:243)
> at org.eclipse.jface.dialogs.TitleAreaDialog.createContents(TitleAreaDialog.java:159)
> at org.eclipse.jface.window.Window.create(Window.java:432)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1104)
> at org.eclipse.jface.window.Window.open(Window.java:791)
> at org.teiid.designer.runtime.ui.wizards.webservices.RestWarDeploymentInfoDialog.open(RestWarDeploymentInfoDialog.java:186)
> at org.teiid.designer.runtime.ui.actions.GenerateRestWarAction.run(GenerateRestWarAction.java:147)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:499)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> So how could i to find what happened here?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 4 months
[JBoss JIRA] (TEIIDDES-2001) Problem with New Connection Profile wizard
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2001?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2001.
------------------------------------
Resolution: Done
Done
> Problem with New Connection Profile wizard
> ------------------------------------------
>
> Key: TEIIDDES-2001
> URL: https://issues.jboss.org/browse/TEIIDDES-2001
> Project: Teiid Designer
> Issue Type: Bug
> Components: Datatools Integration, Import/Export, Modeling
> Affects Versions: 8.3
> Reporter: Mark Drilling
> Assignee: Barry LaFond
> Fix For: 8.3.x
>
>
> The 'Finish' button is enabled on the first page of the New Connection Profile wizard. If finish is clicked before going to the next page to enter info, results in the following npe:
> java.lang.NullPointerException
> at org.eclipse.datatools.connectivity.ui.wizards.NewConnectionProfileWizardPage.getRepository(NewConnectionProfileWizardPage.java:374)
> at org.eclipse.datatools.connectivity.ui.wizards.NewConnectionProfileWizard.doFinish(NewConnectionProfileWizard.java:115)
> at org.eclipse.datatools.connectivity.ui.wizards.NewConnectionProfileWizard.performFinish(NewConnectionProfileWizard.java:96)
> at org.eclipse.datatools.connectivity.internal.ui.wizards.NewCPWizard.performFinish(NewCPWizard.java:95)
> at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:827)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:432)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 4 months
[JBoss JIRA] (TEIIDDES-1971) Connection Reset by Peer messages appearing in JBoss log
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1971?page=com.atlassian.jira.plu... ]
Paul Richardson commented on TEIIDDES-1971:
-------------------------------------------
Possible solution at
https://github.com/Teiid-Designer/teiid-designer/pull/276
Essentially rather than closing the socket immediately, it uses the connection to get some data. Testing has shown that the hostname is returned (in my case 'localhost') so I have logged this then close the connection. More comprehensive testing to determine whether this is a viable solution.
{code}
socket = new Socket();
socket.connect(endPoint, 1024);
InputStream socketReader = socket.getInputStream();
final char[] buffer = new char[100];
in = new InputStreamReader(socketReader);
int rsz = in.read(buffer, 0, buffer.length);
if (rsz == -1)
return false;
StringBuffer output = new StringBuffer();
for (int i = 0; i < buffer.length; ++i) {
if (Character.isLetterOrDigit(buffer[i])) {
output.append(buffer[i]);
}
}
String message = DqpPlugin.Util.getString("jbossServerHeartBeat", host, port, output); //$NON-NLS-1$
IStatus status = new Status(IStatus.OK, DqpPlugin.PLUGIN_ID, message);
DqpPlugin.getInstance().getLog().log(status);
{code}
> Connection Reset by Peer messages appearing in JBoss log
> --------------------------------------------------------
>
> Key: TEIIDDES-1971
> URL: https://issues.jboss.org/browse/TEIIDDES-1971
> Project: Teiid Designer
> Issue Type: Bug
> Reporter: Steven Hawkins
> Assignee: Paul Richardson
> Priority: Critical
> Fix For: 8.4
>
> Attachments: retransmission-packet.png, server.log
>
>
> Running Developer Studio 7.1.0.CR1 and using either the server auto-detection or manually defining a server -and using an incorrect management password- results in a console log entry:
> 14:00:54,966 ERROR [org.jboss.remoting.remote.connection] (Remoting "..." read-1) JBREM000200: Remote connection failed: java.io.IOException: Connection reset by peer
> On server startup without any indication of what it means.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 4 months
[JBoss JIRA] (TEIIDDES-2001) Problem with New Connection Profile wizard
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2001?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2001:
-----------------------------------
Fix Version/s: 8.3.x
Component/s: Datatools Integration
Import/Export
> Problem with New Connection Profile wizard
> ------------------------------------------
>
> Key: TEIIDDES-2001
> URL: https://issues.jboss.org/browse/TEIIDDES-2001
> Project: Teiid Designer
> Issue Type: Bug
> Components: Datatools Integration, Import/Export, Modeling
> Affects Versions: 8.3
> Reporter: Mark Drilling
> Assignee: Barry LaFond
> Fix For: 8.3.x
>
>
> The 'Finish' button is enabled on the first page of the New Connection Profile wizard. If finish is clicked before going to the next page to enter info, results in the following npe:
> java.lang.NullPointerException
> at org.eclipse.datatools.connectivity.ui.wizards.NewConnectionProfileWizardPage.getRepository(NewConnectionProfileWizardPage.java:374)
> at org.eclipse.datatools.connectivity.ui.wizards.NewConnectionProfileWizard.doFinish(NewConnectionProfileWizard.java:115)
> at org.eclipse.datatools.connectivity.ui.wizards.NewConnectionProfileWizard.performFinish(NewConnectionProfileWizard.java:96)
> at org.eclipse.datatools.connectivity.internal.ui.wizards.NewCPWizard.performFinish(NewCPWizard.java:95)
> at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:827)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:432)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 4 months
[JBoss JIRA] (TEIIDDES-2001) Problem with New Connection Profile wizard
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2001?page=com.atlassian.jira.plu... ]
Barry LaFond reassigned TEIIDDES-2001:
--------------------------------------
Assignee: Barry LaFond
> Problem with New Connection Profile wizard
> ------------------------------------------
>
> Key: TEIIDDES-2001
> URL: https://issues.jboss.org/browse/TEIIDDES-2001
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 8.3
> Reporter: Mark Drilling
> Assignee: Barry LaFond
>
> The 'Finish' button is enabled on the first page of the New Connection Profile wizard. If finish is clicked before going to the next page to enter info, results in the following npe:
> java.lang.NullPointerException
> at org.eclipse.datatools.connectivity.ui.wizards.NewConnectionProfileWizardPage.getRepository(NewConnectionProfileWizardPage.java:374)
> at org.eclipse.datatools.connectivity.ui.wizards.NewConnectionProfileWizard.doFinish(NewConnectionProfileWizard.java:115)
> at org.eclipse.datatools.connectivity.ui.wizards.NewConnectionProfileWizard.performFinish(NewConnectionProfileWizard.java:96)
> at org.eclipse.datatools.connectivity.internal.ui.wizards.NewCPWizard.performFinish(NewCPWizard.java:95)
> at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:827)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:432)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 4 months
[JBoss JIRA] (TEIIDDES-2004) NPE seen in error log and causing issues with deploying VDB
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2004?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2004.
------------------------------------
Resolution: Rejected
logged NPE was unrelated to the action of Deploying a VDB. Need to have specific state or workspace and a repeatable info on what the workspace selection was and what view/part or focus event fired the selection event
> NPE seen in error log and causing issues with deploying VDB
> -----------------------------------------------------------
>
> Key: TEIIDDES-2004
> URL: https://issues.jboss.org/browse/TEIIDDES-2004
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 8.3.x
> Reporter: Van Halbert
> Assignee: Barry LaFond
>
> Getting this NPE when trying to deploy VDB:
> java.lang.NullPointerException
> at org.teiid.core.designer.util.PluginUtilImpl.log(PluginUtilImpl.java:245)
> at org.teiid.core.designer.util.PluginUtilImpl.log(PluginUtilImpl.java:275)
> at org.teiid.designer.ui.actions.PasteInResourceAction$ResourcePasteAction.updateSelection(PasteInResourceAction.java:462)
> at org.eclipse.ui.actions.BaseSelectionListenerAction.selectionChanged(BaseSelectionListenerAction.java:124)
> at org.teiid.designer.ui.actions.PasteInResourceAction.selectionChanged(PasteInResourceAction.java:212)
> at org.eclipse.ui.internal.e4.compatibility.SelectionService.notifyListeners(SelectionService.java:154)
> at org.eclipse.ui.internal.e4.compatibility.SelectionService.access$3(SelectionService.java:151)
> at org.eclipse.ui.internal.e4.compatibility.SelectionService$1.selectionChanged(SelectionService.java:74)
> at org.eclipse.e4.ui.internal.workbench.SelectionAggregator$2.run(SelectionAggregator.java:119)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 4 months
[JBoss JIRA] (TEIIDDES-2004) NPE seen in error log and causing issues with deploying VDB
by Van Halbert (JIRA)
Van Halbert created TEIIDDES-2004:
-------------------------------------
Summary: NPE seen in error log and causing issues with deploying VDB
Key: TEIIDDES-2004
URL: https://issues.jboss.org/browse/TEIIDDES-2004
Project: Teiid Designer
Issue Type: Bug
Components: Modeling
Affects Versions: 8.3.x
Reporter: Van Halbert
Assignee: Barry LaFond
Getting this NPE when trying to deploy VDB:
java.lang.NullPointerException
at org.teiid.core.designer.util.PluginUtilImpl.log(PluginUtilImpl.java:245)
at org.teiid.core.designer.util.PluginUtilImpl.log(PluginUtilImpl.java:275)
at org.teiid.designer.ui.actions.PasteInResourceAction$ResourcePasteAction.updateSelection(PasteInResourceAction.java:462)
at org.eclipse.ui.actions.BaseSelectionListenerAction.selectionChanged(BaseSelectionListenerAction.java:124)
at org.teiid.designer.ui.actions.PasteInResourceAction.selectionChanged(PasteInResourceAction.java:212)
at org.eclipse.ui.internal.e4.compatibility.SelectionService.notifyListeners(SelectionService.java:154)
at org.eclipse.ui.internal.e4.compatibility.SelectionService.access$3(SelectionService.java:151)
at org.eclipse.ui.internal.e4.compatibility.SelectionService$1.selectionChanged(SelectionService.java:74)
at org.eclipse.e4.ui.internal.workbench.SelectionAggregator$2.run(SelectionAggregator.java:119)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 4 months
[JBoss JIRA] (TEIIDDES-2003) Usability - In a model, group by types (i.e, Table, procedure, etc.)
by Van Halbert (JIRA)
Van Halbert created TEIIDDES-2003:
-------------------------------------
Summary: Usability - In a model, group by types (i.e, Table, procedure, etc.)
Key: TEIIDDES-2003
URL: https://issues.jboss.org/browse/TEIIDDES-2003
Project: Teiid Designer
Issue Type: Feature Request
Components: Modeling
Affects Versions: 8.3
Reporter: Van Halbert
>From a usability standpoint, and when working with large models, it would good to group by type (i.e, Table, procedure, etc.) when laying out a model in the tree on the left.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 4 months
[JBoss JIRA] (TEIIDDES-1944) Refreshing a server that's not started results in Exception & dialog
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1944?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration commented on TEIIDDES-1944:
---------------------------------------------------
Nick Cross <ncross(a)redhat.com> changed the Status of [bug 1035473|https://bugzilla.redhat.com/show_bug.cgi?id=1035473] from MODIFIED to ON_QA
> Refreshing a server that's not started results in Exception & dialog
> --------------------------------------------------------------------
>
> Key: TEIIDDES-1944
> URL: https://issues.jboss.org/browse/TEIIDDES-1944
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Affects Versions: 8.3
> Reporter: Barry LaFond
> Assignee: Paul Richardson
> Fix For: 8.3
>
>
> With single defined Server & Teiid instance.... I can generate same error in RefeshServerAction
> *Case 1:* Select server and click *Refesh* toolbar button
> Result:
> java.lang.Exception: The parent JBoss Server is not started.
> at org.teiid.designer.runtime.TeiidServer.reconnect(TeiidServer.java:218)
> at org.teiid.designer.runtime.ui.server.RefreshServerAction$1.run(RefreshServerAction.java:84)
> 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:3717)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3366)
> 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.RefreshServerAction.run(RefreshServerAction.java:80)
> at org.teiid.designer.runtime.ui.server.RefreshServerAction.execute(RefreshServerAction.java:127)
>
> ==============
> *Case 2:* In Guides View > Teiid (action set) select *Refresh Teiid Instance*
> Results:
> java.lang.Exception: The parent JBoss Server is not started.
> at org.teiid.designer.runtime.TeiidServer.reconnect(TeiidServer.java:218)
> at org.teiid.designer.runtime.ui.server.RefreshServerAction$1.run(RefreshServerAction.java:84)
> 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:3717)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3366)
> 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.RefreshServerAction.run(RefreshServerAction.java:80)
> at org.teiid.designer.runtime.ui.server.RuntimeAssistant.runRefreshServerAction(RuntimeAssistant.java:186)
> at org.teiid.designer.advisor.ui.actions.AdvisorActionFactory.executeAction(AdvisorActionFactory.java:632)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 4 months
[JBoss JIRA] (TEIIDDES-1918) JDBC importer adds wrong column type for columns of type integer, when importing(Reusing) VDB
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1918?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration commented on TEIIDDES-1918:
---------------------------------------------------
Nick Cross <ncross(a)redhat.com> changed the Status of [bug 1026892|https://bugzilla.redhat.com/show_bug.cgi?id=1026892] from MODIFIED to ON_QA
> JDBC importer adds wrong column type for columns of type integer, when importing(Reusing) VDB
> ----------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1918
> URL: https://issues.jboss.org/browse/TEIIDDES-1918
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.3
> Reporter: Van Halbert
> Assignee: Mark Drilling
> Priority: Critical
> Fix For: 8.3
>
>
> When a VDB is imported(reused) by another VDB and the imported VDB contains table with column of type integer, then the importing VDB will throw validation error.
> Steps to reproduce:
> 1. Create loopback VDB, add table DATA with two columns, one of type integer and one of the string
> 2. Deploy the loopback VDB
> 3. Reuse the looback VDB
> 3.1. Import the loopback VDB through JDBC importer
> "Import as VDB source model" have to be checked
> 3.2 Create view model, use table DATA in the view model
> 3.3 Create and deploy new VDB
> When deploying the VDB, error occures:
> TEIID31080 View data validation error: QueryValidatorException-The definition for data has the wrong type for column 1. Expected bigdecimal, but was biginteger.
> 15:57:48,718 INFO [org.teiid.RUNTIME] (teiid-async-threads - 1) TEIID40073 The metadata for the VDB aaa.1 is loaded, however it is not valid. Check models for errors. Correct the metadata and re-deploy.
> 15:57:48,719 INFO [org.teiid.RUNTIME] (teiid-async-threads - 1) TEIID40003 VDB aaa.1 is set to FAILED
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 4 months