December 2018 - jbosstools-issues

[JBoss JIRA] (JBIDE-26391) Create New and Noteworthy for 4.10.0.AM1

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26391?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26391: ------------------------------- Sprint: devex #156 October 2018, devex #157 November 2019, devex #158 November 2018 (was: devex #156 October 2018, devex #157 November 2019, devex #158 November 2018, devex #159 December 2018) > Create New and Noteworthy for 4.10.0.AM1 > ---------------------------------------- > > Key: JBIDE-26391 > URL: https://issues.jboss.org/browse/JBIDE-26391 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.11.0.AM1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for all N&N. See subtasks below. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26158) [UPSTREAM] Server adapter: NPE when starting adapter for nodejs-mongo-persistent into Debug

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26158?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26158: ------------------------------- Sprint: devex #156 October 2018, devex #157 November 2019, devex #158 November 2018 (was: devex #156 October 2018, devex #157 November 2019, devex #158 November 2018, devex #159 December 2018) > [UPSTREAM] Server adapter: NPE when starting adapter for nodejs-mongo-persistent into Debug > -------------------------------------------------------------------------------------------- > > Key: JBIDE-26158 > URL: https://issues.jboss.org/browse/JBIDE-26158 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.6.0.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Major > Labels: upstream > Fix For: 4.11.x > > Attachments: image-2018-07-02-22-33-13-396.png, image-2018-07-02-22-49-45-246.png, image-2018-07-02-23-17-34-099.png, image-2018-07-03-00-03-56-346.png, screenshot-1.png, screenshot-2.png > > > steps: > # EXEC: launch new application wizard, choose nodejs-mongo-persistent template and finish > # EXEC: when asked import the app and create a server adapter > # ASSERT: server adapter is created > # EXEC: start the server adapter > # ASSERT: server adapter is launched > # EXEC: restart the server adapter into Debug > Result: > Debuggin works, but you get the following error dialog: > !image-2018-07-02-22-33-13-396.png! > In the Eclipse log you'll find the following: > {code} > java.lang.NullPointerException > at org.eclipse.core.internal.resources.CheckMissingNaturesListener.updateRange(CheckMissingNaturesListener.java:209) > at org.eclipse.core.internal.resources.CheckMissingNaturesListener$3.runInWorkspace(CheckMissingNaturesListener.java:179) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60) > {code} > ps. project context menu: Convert > Javascript Project doesn't help. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[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, devex #158 November 2018 (was: devex #155 September 2018, devex #156 October 2018, devex #157 November 2019, devex #158 November 2018, devex #159 December 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.11.x > > 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)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26406) Update server integration tests to include EAP 7.2 Beta

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26406?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26406: ------------------------------- Sprint: devex #156 October 2018, devex #157 November 2019, devex #158 November 2018 (was: devex #156 October 2018, devex #157 November 2019, devex #158 November 2018, devex #159 December 2018) > Update server integration tests to include EAP 7.2 Beta > ------------------------------------------------------- > > Key: JBIDE-26406 > URL: https://issues.jboss.org/browse/JBIDE-26406 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.9.0.Final > Reporter: Jeff MAURY > Assignee: Rob Stryker > Priority: Major > Labels: EAP, EAP_7, server > Fix For: 4.11.x > > > EAP 7.2 Beta is out since August 26th. We should update the server integration tests so that EAP QE can use our integration tests against it -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25000) Server adapter: starting into debugging fails initially (succeeds on a latter try)

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-25000?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25000: ------------------------------- Sprint: devex #138 September 2017, devex #152 July 2018, devex #153 August 2018, devex #154 September 2018, devex #155 September 2018, devex #156 October 2018, devex #157 November 2019, devex #158 November 2018 (was: devex #138 September 2017, devex #152 July 2018, devex #153 August 2018, devex #154 September 2018, devex #155 September 2018, devex #156 October 2018, devex #157 November 2019, devex #158 November 2018, devex #159 December 2018) > Server adapter: starting into debugging fails initially (succeeds on a latter try) > ---------------------------------------------------------------------------------- > > Key: JBIDE-25000 > URL: https://issues.jboss.org/browse/JBIDE-25000 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.0.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Major > Labels: openshift_v3, server_adapter > Fix For: 4.11.x > > Attachments: failed-to-connect-v8-vm.png > > > # ASSERT: have an application running in *[OpenShift Online|https://console.starter-us-east-2.openshift.com/]* based on the "nodejs-mongo-persistent" template > # ASSERT: have a server adapter for it > # EXEC/ASSERT: have the adapter started in non-debugging/normal mode > # EXEC: restart the adapter debugging > Result: > !failed-to-connect-v8-vm.png! > {code} > java.io.IOException: Failed to get version > 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:132) > 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:885) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039) > at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > Caused by: java.util.concurrent.ExecutionException: java.io.IOException: End of stream > at java.util.concurrent.FutureTask.report(FutureTask.java:122) > at java.util.concurrent.FutureTask.get(FutureTask.java:206) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:127) > ... 9 more > Caused by: java.io.IOException: End of stream > at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:127) > at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl.perform(Handshaker.java:104) > at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection$ReaderThread.run(SocketConnection.java:158) > {code} > ps. this can be simulated in the CDK, by having everything set and once the pod is up and ithe adapter is in debug, stopping the port forwarding. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26158) [UPSTREAM] Server adapter: NPE when starting adapter for nodejs-mongo-persistent into Debug

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26158?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26158: ------------------------------- Sprint: devex #156 October 2018, devex #157 November 2019, devex #158 November 2018, devex #159 December 2018 (was: devex #156 October 2018, devex #157 November 2019, devex #158 November 2018) > [UPSTREAM] Server adapter: NPE when starting adapter for nodejs-mongo-persistent into Debug > -------------------------------------------------------------------------------------------- > > Key: JBIDE-26158 > URL: https://issues.jboss.org/browse/JBIDE-26158 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.6.0.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Major > Labels: upstream > Fix For: 4.11.x > > Attachments: image-2018-07-02-22-33-13-396.png, image-2018-07-02-22-49-45-246.png, image-2018-07-02-23-17-34-099.png, image-2018-07-03-00-03-56-346.png, screenshot-1.png, screenshot-2.png > > > steps: > # EXEC: launch new application wizard, choose nodejs-mongo-persistent template and finish > # EXEC: when asked import the app and create a server adapter > # ASSERT: server adapter is created > # EXEC: start the server adapter > # ASSERT: server adapter is launched > # EXEC: restart the server adapter into Debug > Result: > Debuggin works, but you get the following error dialog: > !image-2018-07-02-22-33-13-396.png! > In the Eclipse log you'll find the following: > {code} > java.lang.NullPointerException > at org.eclipse.core.internal.resources.CheckMissingNaturesListener.updateRange(CheckMissingNaturesListener.java:209) > at org.eclipse.core.internal.resources.CheckMissingNaturesListener$3.runInWorkspace(CheckMissingNaturesListener.java:179) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60) > {code} > ps. project context menu: Convert > Javascript Project doesn't help. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[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, devex #158 November 2018, devex #159 December 2018 (was: devex #155 September 2018, devex #156 October 2018, devex #157 November 2019, devex #158 November 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.11.x > > 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)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26391) Create New and Noteworthy for 4.10.0.AM1

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26391?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26391: ------------------------------- Sprint: devex #156 October 2018, devex #157 November 2019, devex #158 November 2018, devex #159 December 2018 (was: devex #156 October 2018, devex #157 November 2019, devex #158 November 2018) > Create New and Noteworthy for 4.10.0.AM1 > ---------------------------------------- > > Key: JBIDE-26391 > URL: https://issues.jboss.org/browse/JBIDE-26391 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.11.0.AM1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for all N&N. See subtasks below. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26406) Update server integration tests to include EAP 7.2 Beta

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26406?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26406: ------------------------------- Sprint: devex #156 October 2018, devex #157 November 2019, devex #158 November 2018, devex #159 December 2018 (was: devex #156 October 2018, devex #157 November 2019, devex #158 November 2018) > Update server integration tests to include EAP 7.2 Beta > ------------------------------------------------------- > > Key: JBIDE-26406 > URL: https://issues.jboss.org/browse/JBIDE-26406 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.9.0.Final > Reporter: Jeff MAURY > Assignee: Rob Stryker > Priority: Major > Labels: EAP, EAP_7, server > Fix For: 4.11.x > > > EAP 7.2 Beta is out since August 26th. We should update the server integration tests so that EAP QE can use our integration tests against it -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[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, devex #158 November 2018, devex #159 December 2018 (was: devex #156 October 2018, devex #157 November 2019, devex #158 November 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.11.x > > 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)

5 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2018