[JBoss JIRA] (JBIDE-26450) Server ITests: Investigate failure in org.jboss.tools.as.itests
by Josef Kopriva (Jira)
Josef Kopriva created JBIDE-26450:
-------------------------------------
Summary: Server ITests: Investigate failure in org.jboss.tools.as.itests
Key: JBIDE-26450
URL: https://issues.jboss.org/browse/JBIDE-26450
Project: Tools (JBoss Tools)
Issue Type: Task
Components: integration-tests, server
Affects Versions: 4.10.0.AM1
Reporter: Josef Kopriva
Assignee: Josef Kopriva
Fix For: 4.10.0.AM1
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
{code:java}
org.jboss.tools.as.itests.ServerBeanLoaderIntegrationTest.testServerBeanLoaderFromRuntimes[org.jboss.ide.eclipse.as.wildfly.140]Failed with 0 retries
Error Details
Expected and actual server beans do not match for server type org.jboss.ide.eclipse.as.wildfly.140 expected:<WildFly> but was:<WildFly>
Stack Trace
junit.framework.AssertionFailedError: Expected and actual server beans do not match for server type org.jboss.ide.eclipse.as.wildfly.140 expected:<WildFly> but was:<WildFly>
at org.jboss.tools.as.itests.ServerBeanLoaderIntegrationTest.testServerBeanLoaderFromRuntimes(ServerBeanLoaderIntegrationTest.java:69)
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (JBIDE-26450) Server ITests: Investigate failure in org.jboss.tools.as.itests
by Josef Kopriva (Jira)
[ https://issues.jboss.org/browse/JBIDE-26450?page=com.atlassian.jira.plugi... ]
Josef Kopriva updated JBIDE-26450:
----------------------------------
Story Points: 5
> Server ITests: Investigate failure in org.jboss.tools.as.itests
> ---------------------------------------------------------------
>
> Key: JBIDE-26450
> URL: https://issues.jboss.org/browse/JBIDE-26450
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests, server
> Affects Versions: 4.10.0.AM1
> Reporter: Josef Kopriva
> Assignee: Josef Kopriva
> Priority: Major
> Fix For: 4.10.0.AM1
>
>
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> {code:java}
> org.jboss.tools.as.itests.ServerBeanLoaderIntegrationTest.testServerBeanLoaderFromRuntimes[org.jboss.ide.eclipse.as.wildfly.140]Failed with 0 retries
> Error Details
> Expected and actual server beans do not match for server type org.jboss.ide.eclipse.as.wildfly.140 expected:<WildFly> but was:<WildFly>
> Stack Trace
> junit.framework.AssertionFailedError: Expected and actual server beans do not match for server type org.jboss.ide.eclipse.as.wildfly.140 expected:<WildFly> but was:<WildFly>
> at org.jboss.tools.as.itests.ServerBeanLoaderIntegrationTest.testServerBeanLoaderFromRuntimes(ServerBeanLoaderIntegrationTest.java:69)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (JBIDE-26311) EAP 7.1 fails to stop when connected over ssh
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26311?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26311:
-------------------------------
Sprint: devex #155 September 2018, devex #156 October 2018, devex #157 November 2019 (was: devex #155 September 2018, devex #156 October 2018)
> EAP 7.1 fails to stop when connected over ssh
> ---------------------------------------------
>
> Key: JBIDE-26311
> URL: https://issues.jboss.org/browse/JBIDE-26311
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.9.0.AM2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Major
> Labels: regression
> Fix For: 4.10.0.AM1
>
> Attachments: JBIDE-26311.local.ogv
>
>
> I have an EAP 7.1 setup up over ssh. It's running on my localhost, so it's the most basic test of an ssh server. When I click the stop button on the server, it says:
> Server Red Hat JBoss EAP 7.1 ssh failed to stop.
> An exception stack trace is not available.
> It will stop on second attempt. On a local server this would mean killing the server java process. I'm not sure exactly what happens on a remote server, but it works.
> I'm pretty sure this worked last time (previous milestone).
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (JBIDE-26408) Server adapter: debugging fails for nodejs-mongo-persistent template based application
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26408?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26408:
-------------------------------
Sprint: devex #156 October 2018, devex #157 November 2019 (was: devex #156 October 2018)
> Server adapter: debugging fails for nodejs-mongo-persistent template based application
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-26408
> URL: https://issues.jboss.org/browse/JBIDE-26408
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.9.0.Final
> Environment: cdk-3.6.0
> Reporter: Andre Dietisheim
> Assignee: Jeff MAURY
> Priority: Major
> Labels: node, server_adapter
> Fix For: 4.10.0.AM1
>
> Attachments: change-nodejs-version.png, screenshot-1.png, screenshot-2.png
>
>
> steps:
> # ASSERT: have cdk 3.6.0
> # EXEC: create an application based on the *nodejs-mongo-persistent* template, have the application imported to the workspace and the server adapter created for it
> # EXEC: start the server adapter
> # ASSERT: server adapter is *[Started, Synchronized]*
> # EXEC: Restart the adapter into debugging
> Result:
> You very quickly (the timeout seems very short) get an error dialog telling you that the debugger could not connect.
> !screenshot-1.png!
> The debugger is therefore stopped, debugging wont work.
> !screenshot-2.png!
> Trying to restart it reproduces the error that we already have.
> In the Eclipse log you'll find the following:
> {code}
> java.io.IOException: Timed out waiting for handshake
> at org.eclipse.wst.jsdt.chromium.internal.v8native.JavascriptVmImpl.newIOException(JavascriptVmImpl.java:114)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:134)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attach(StandaloneVmImpl.java:79)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.JavascriptVmEmbedderFactory$4$1.attach(JavascriptVmEmbedderFactory.java:207)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.DebugTargetImpl.attach(DebugTargetImpl.java:74)
> at org.eclipse.wst.jsdt.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:101)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:859)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:717)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1026)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$2.run(DebugUIPlugin.java:1240)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60)
> Caused by: java.util.concurrent.TimeoutException
> at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:204)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:127)
> ... 9 more
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months