February 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-22075) Confusing error message when trying to attach remote debugger to OS app run in debug mode

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22075?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22075: ------------------------------------- Sprint: (was: devex #128 February 2017) > Confusing error message when trying to attach remote debugger to OS app run in debug mode > ----------------------------------------------------------------------------------------- > > Key: JBIDE-22075 > URL: https://issues.jboss.org/browse/JBIDE-22075 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: debugging, openshift_v3 > Fix For: 4.5.0.AM1 > > Attachments: debug-button-toolbar.png, error-in-launching-remote-debugger.png, error-launching-remote-debugger.png, launch-debug-no-error.mov, remote-debugger-already-launched.png > > > If you restart the server adapter in debug mode ("Restart in Debug" in the context menu to your server adapter) the remote debugger is launched automatically. > If you're not aware of this and try to launch the remote debugger entry (that was created automatically), you will face an error telling you that it cannot connect (since there's already an instance sitting on the ports). It's not obvious to the dummy user, we should improve this error-message > When I am trying to run remote debugging of an application on OpenShift I get following error > !!error-in-launching-remote-debugger.png! ! > {code} > Failed to connect to remote VM > com.sun.jdi.connect.spi.ClosedConnectionException > at org.eclipse.jdi.internal.connect.SocketTransportService.readHandshake(SocketTransportService.java:222) > at org.eclipse.jdi.internal.connect.SocketTransportService.access$7(SocketTransportService.java:214) > at org.eclipse.jdi.internal.connect.SocketTransportService$3.run(SocketTransportService.java:185) > at java.lang.Thread.run(Thread.java:745) > {code} > *Steps to reproduce:* > ASSERT: Have an OpenShift 3 application based on eap 6 template with server adapter and project in workspace. > EXEC: Select "Restart in Debug" in context menu of server adapter. > ASSERT: Server adapter is in state debugging ("[Debugging, Started]"). > EXEC: Click on Debug Remote debugger to 'server adapter name' workbench tool item to start debugging. > RESULT: Error is shown. > EXPECTED RESULT: The error message should tell you that there already is an instance running. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-22075) Confusing error message when trying to attach remote debugger to OS app run in debug mode

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22075?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22075: ------------------------------------------ I cant reproduce this, thus postponing it. > Confusing error message when trying to attach remote debugger to OS app run in debug mode > ----------------------------------------------------------------------------------------- > > Key: JBIDE-22075 > URL: https://issues.jboss.org/browse/JBIDE-22075 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: debugging, openshift_v3 > Fix For: 4.5.0.AM1 > > Attachments: debug-button-toolbar.png, error-in-launching-remote-debugger.png, error-launching-remote-debugger.png, launch-debug-no-error.mov, remote-debugger-already-launched.png > > > If you restart the server adapter in debug mode ("Restart in Debug" in the context menu to your server adapter) the remote debugger is launched automatically. > If you're not aware of this and try to launch the remote debugger entry (that was created automatically), you will face an error telling you that it cannot connect (since there's already an instance sitting on the ports). It's not obvious to the dummy user, we should improve this error-message > When I am trying to run remote debugging of an application on OpenShift I get following error > !!error-in-launching-remote-debugger.png! ! > {code} > Failed to connect to remote VM > com.sun.jdi.connect.spi.ClosedConnectionException > at org.eclipse.jdi.internal.connect.SocketTransportService.readHandshake(SocketTransportService.java:222) > at org.eclipse.jdi.internal.connect.SocketTransportService.access$7(SocketTransportService.java:214) > at org.eclipse.jdi.internal.connect.SocketTransportService$3.run(SocketTransportService.java:185) > at java.lang.Thread.run(Thread.java:745) > {code} > *Steps to reproduce:* > ASSERT: Have an OpenShift 3 application based on eap 6 template with server adapter and project in workspace. > EXEC: Select "Restart in Debug" in context menu of server adapter. > ASSERT: Server adapter is in state debugging ("[Debugging, Started]"). > EXEC: Click on Debug Remote debugger to 'server adapter name' workbench tool item to start debugging. > RESULT: Error is shown. > EXPECTED RESULT: The error message should tell you that there already is an instance running. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-22075) Confusing error message when trying to attach remote debugger to OS app run in debug mode

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22075?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22075: ------------------------------------- Fix Version/s: 4.5.0.AM1 > Confusing error message when trying to attach remote debugger to OS app run in debug mode > ----------------------------------------------------------------------------------------- > > Key: JBIDE-22075 > URL: https://issues.jboss.org/browse/JBIDE-22075 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: debugging, openshift_v3 > Fix For: 4.5.0.AM1 > > Attachments: debug-button-toolbar.png, error-in-launching-remote-debugger.png, error-launching-remote-debugger.png, launch-debug-no-error.mov, remote-debugger-already-launched.png > > > If you restart the server adapter in debug mode ("Restart in Debug" in the context menu to your server adapter) the remote debugger is launched automatically. > If you're not aware of this and try to launch the remote debugger entry (that was created automatically), you will face an error telling you that it cannot connect (since there's already an instance sitting on the ports). It's not obvious to the dummy user, we should improve this error-message > When I am trying to run remote debugging of an application on OpenShift I get following error > !!error-in-launching-remote-debugger.png! ! > {code} > Failed to connect to remote VM > com.sun.jdi.connect.spi.ClosedConnectionException > at org.eclipse.jdi.internal.connect.SocketTransportService.readHandshake(SocketTransportService.java:222) > at org.eclipse.jdi.internal.connect.SocketTransportService.access$7(SocketTransportService.java:214) > at org.eclipse.jdi.internal.connect.SocketTransportService$3.run(SocketTransportService.java:185) > at java.lang.Thread.run(Thread.java:745) > {code} > *Steps to reproduce:* > ASSERT: Have an OpenShift 3 application based on eap 6 template with server adapter and project in workspace. > EXEC: Select "Restart in Debug" in context menu of server adapter. > ASSERT: Server adapter is in state debugging ("[Debugging, Started]"). > EXEC: Click on Debug Remote debugger to 'server adapter name' workbench tool item to start debugging. > RESULT: Error is shown. > EXPECTED RESULT: The error message should tell you that there already is an instance running. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-22075) Confusing error message when trying to attach remote debugger to OS app run in debug mode

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22075?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22075: ------------------------------------- Fix Version/s: (was: 4.4.4.AM1) > Confusing error message when trying to attach remote debugger to OS app run in debug mode > ----------------------------------------------------------------------------------------- > > Key: JBIDE-22075 > URL: https://issues.jboss.org/browse/JBIDE-22075 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: debugging, openshift_v3 > Fix For: 4.5.0.AM1 > > Attachments: debug-button-toolbar.png, error-in-launching-remote-debugger.png, error-launching-remote-debugger.png, launch-debug-no-error.mov, remote-debugger-already-launched.png > > > If you restart the server adapter in debug mode ("Restart in Debug" in the context menu to your server adapter) the remote debugger is launched automatically. > If you're not aware of this and try to launch the remote debugger entry (that was created automatically), you will face an error telling you that it cannot connect (since there's already an instance sitting on the ports). It's not obvious to the dummy user, we should improve this error-message > When I am trying to run remote debugging of an application on OpenShift I get following error > !!error-in-launching-remote-debugger.png! ! > {code} > Failed to connect to remote VM > com.sun.jdi.connect.spi.ClosedConnectionException > at org.eclipse.jdi.internal.connect.SocketTransportService.readHandshake(SocketTransportService.java:222) > at org.eclipse.jdi.internal.connect.SocketTransportService.access$7(SocketTransportService.java:214) > at org.eclipse.jdi.internal.connect.SocketTransportService$3.run(SocketTransportService.java:185) > at java.lang.Thread.run(Thread.java:745) > {code} > *Steps to reproduce:* > ASSERT: Have an OpenShift 3 application based on eap 6 template with server adapter and project in workspace. > EXEC: Select "Restart in Debug" in context menu of server adapter. > ASSERT: Server adapter is in state debugging ("[Debugging, Started]"). > EXEC: Click on Debug Remote debugger to 'server adapter name' workbench tool item to start debugging. > RESULT: Error is shown. > EXPECTED RESULT: The error message should tell you that there already is an instance running. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-24016) Server adapter, integration tests: assert debugging scenarios

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24016?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-24016: ------------------------------------------ [~rhopp] can you please estimate and schedule this one? > Server adapter, integration tests: assert debugging scenarios > ------------------------------------------------------------- > > Key: JBIDE-24016 > URL: https://issues.jboss.org/browse/JBIDE-24016 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: integration-tests, openshift > Affects Versions: 4.4.3.Final > Reporter: Andre Dietisheim > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-24017) Server adapter, integration tests: assert publishing scenarios

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24017?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-24017: ------------------------------------------ [~rhopp] can you please estimate and schedule this one? > Server adapter, integration tests: assert publishing scenarios > -------------------------------------------------------------- > > Key: JBIDE-24017 > URL: https://issues.jboss.org/browse/JBIDE-24017 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: integration-tests, openshift > Affects Versions: 4.4.3.Final > Reporter: Andre Dietisheim > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-24017) Server adapter, integration tests: assert publishing scenarios

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-24017: ---------------------------------------- Summary: Server adapter, integration tests: assert publishing scenarios Key: JBIDE-24017 URL: https://issues.jboss.org/browse/JBIDE-24017 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: integration-tests, openshift Affects Versions: 4.4.3.Final Reporter: Andre Dietisheim -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-24016) Server adapter, integration tests: assert debugging scenarios

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-24016: ---------------------------------------- Summary: Server adapter, integration tests: assert debugging scenarios Key: JBIDE-24016 URL: https://issues.jboss.org/browse/JBIDE-24016 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: integration-tests, openshift Affects Versions: 4.4.3.Final Reporter: Andre Dietisheim -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23057) Integration tests: test import project in server adapter wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23057?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23057: ------------------------------------- Component/s: integration-tests > Integration tests: test import project in server adapter wizard > --------------------------------------------------------------- > > Key: JBIDE-23057 > URL: https://issues.jboss.org/browse/JBIDE-23057 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.5.0.AM1 > > > JBIDE-22621 allows the user to import a project in the server adapter wizard. We should add an integration test for this scenarion in CreateServerAdapterTest -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23890) Application Wizard: Finish is enabled after selecting a builder image, clicking next and then back

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23890?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23890: ------------------------------- Affects Version/s: 4.4.3.AM2 (was: 4.4.4.AM1) > Application Wizard: Finish is enabled after selecting a builder image, clicking next and then back > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-23890 > URL: https://issues.jboss.org/browse/JBIDE-23890 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM2 > Reporter: Jan Richter > Assignee: Jeff MAURY > Labels: application_wizard, openshift_v3 > Fix For: 4.4.4.AM1 > > Attachments: app.png > > > When creating a new application from a builder image, clicking 'next' and then going back again will leave the finish button enabled. > Moreover it will store the image that was selected when next button was clicked so if the user selects a new image and clicks finish, it will still use the original image. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues February 2017