[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:
-------------------------------------------
Confirmed [~burrsutter]'s test conditions.
A vanilla eap6 server is all that is required to create the error message in the log. Therefore, it IS a client / Designer / Teiid Tooling issue.
Investigating this morning, I tentatively think I have pinned it down to JBossServerUtil.isHostConnected(). This tests generically whether a server is available on the given host and port (host being your eap6 server and port being the admin port).
The method does this:
{code}
try {
socket = new Socket();
// Comment out the line below
socket.connect(endPoint, 0);
return true;
} catch (Exception ex) {
ex.printStackTrace();
return false;
} finally {
try {
if (socket != null && socket.isConnected()) {
socket.close();
socket = null;
}
} catch (Exception ex2) {
ex2.printStackTrace();
}
}
{code}
I think that due to the frequency this can be called, eg. its called 3 times when the server start button is clicked, its banging the server too quickly in that its saying server.connect() then server.close() immediately and I wonder whether the server is 'running out of breath' to respond hence the error messages server-side (not client-side).
[~blafond], [~mdrillin], can you try repeating the following test:
1) Start vanilla eap6 (no teiid)
2) Open Designer
3) Start server in Server View
4) Review error log, confirming existence of error messages.
5) Quit Designer
6) Restart server - *** important as I think the socket connections are cached and timeout related so error messages don't always appear straight away.
7) Comment out connect line shown above and repeat 1-4 and confirm no error messages.
8) Repeat lots of times to get a firm idea that this is the problem!!
> 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, 6 months
[JBoss JIRA] (TEIIDDES-2002) Got errors when generate Rest wars
by Gang Li (JIRA)
Gang Li created TEIIDDES-2002:
---------------------------------
Summary: 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
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, 6 months
[JBoss JIRA] (TEIIDDES-1971) Connection Reset by Peer messages appearing in JBoss log
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1971?page=com.atlassian.jira.plu... ]
Burr Sutter commented on TEIIDDES-1971:
---------------------------------------
I just have vanilla EAP 6.1 and the LiveReload server configured
> 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, 6 months
[JBoss JIRA] (TEIIDDES-2001) Problem with New Connection Profile wizard
by Mark Drilling (JIRA)
Mark Drilling created TEIIDDES-2001:
---------------------------------------
Summary: 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
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, 6 months
[JBoss JIRA] (TEIIDDES-1971) Connection Reset by Peer messages appearing in JBoss log
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1971?page=com.atlassian.jira.plu... ]
Max Rydahl Andersen commented on TEIIDDES-1971:
-----------------------------------------------
We just had this come up with Burr Sutter reporting the same error - we thought he found a new bug since he was not using teiid not did he think it was installed. But it actually was.
This means Teiid is causing this to happen on all EAP 6/AS7+ servers no matter if teiid is used by the user or not - the user just need to have installed it.
Any luck of tracking this down what the cause is since now it affects more than "just" Teiid usecase.
> 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, 6 months
[JBoss JIRA] (TEIIDDES-1971) Connection Reset by Peer messages appearing in JBoss log
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1971?page=com.atlassian.jira.plu... ]
Burr Sutter commented on TEIIDDES-1971:
---------------------------------------
I have seen this message as well:
JBDS 7.1 GA + all the various SOA tools installed from JBoss Central
EAP 6.1
Teiid Designer Runtime needed to be uninstalled - I also uninstalled Teiid Designer first and saw the message again, so went back and uninstalled the Teiid Designer Runtime.
> 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, 6 months
[JBoss JIRA] (TEIIDDES-1999) Cannot Preview a Model after importing via the Teiid Connection Importer
by Mark Drilling (JIRA)
Mark Drilling created TEIIDDES-1999:
---------------------------------------
Summary: Cannot Preview a Model after importing via the Teiid Connection Importer
Key: TEIIDDES-1999
URL: https://issues.jboss.org/browse/TEIIDDES-1999
Project: Teiid Designer
Issue Type: Enhancement
Components: Import/Export
Affects Versions: 8.3
Reporter: Mark Drilling
Assignee: Mark Drilling
Fix For: 8.3.x
After importing a model via the Teiid Connection Importer, it cannot be previewed - a connection profile must be set first.
Since the importer creates a dataSource on the Teiid Server, we should be able to apply the appropriate connection info to allow this.
--
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, 6 months
[JBoss JIRA] (TEIIDDES-1991) File translator override for encoding defaults to UTF-8 in Designer but doesn't write to the vdb.xml
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1991?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1991:
----------------------------------------
Note the translator override templates won't be available from Teiid admin until Designer is upgraded to use 8.5/8.6 Teiid. So this should be worked in Designer 8.4 release
> File translator override for encoding defaults to UTF-8 in Designer but doesn't write to the vdb.xml
> ----------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1991
> URL: https://issues.jboss.org/browse/TEIIDDES-1991
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Reporter: Debbie Steigner
> Assignee: Barry LaFond
> Fix For: 8.4
>
>
> If you need to override the file translator's encoding value and want to set it to UTF-8, the Designer shows this value as the default so will not write it to the overrides in the vdb.xml and hence the server will not look at it. Can the default in the Designer be blank? so that any value entered will be written as an translator override in the vdb.xml file.
--
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, 6 months