[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)
8 years, 10 months
[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)
8 years, 10 months
[JBoss JIRA] (JBIDE-23900) Refactor OpenShift server adapter to isolate EAP/Wildfly and NodeJS specific stuff
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23900?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23900:
------------------------------------------
Among other issues there is duplication of code where the environment variables are set:
{code:title=https://github.com/jbosstools/jbosstools-openshift/blob/master/plugins/org.jboss.tools.openshift.core/src/org/jboss/tools/openshift/core/server/behavior/OpenShiftLaunchController.java#L211}
deploymentConfig.setEnvironmentVariable(DEV_MODE_KEY, String.valueOf(debugContext.isDebugEnabled()));
{code}
is duplicate to
{code:title=https://github.com/jbosstools/jbosstools-openshift/blob/master/plugins/org.jboss.tools.openshift.core/src/org/jboss/tools/openshift/internal/core/server/debug/OpenShiftDebugUtils.java#L184}
dc.setEnvironmentVariable(DEV_MODE, Boolean.TRUE.toString());
{code}
> Refactor OpenShift server adapter to isolate EAP/Wildfly and NodeJS specific stuff
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-23900
> URL: https://issues.jboss.org/browse/JBIDE-23900
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.3.Final
> Reporter: Jeff MAURY
> Assignee: Dmitrii Bocharov
> Fix For: 4.4.4.AM1
>
>
> We should isolate EAP/Wildfly and NodeJS specific stuff for the server adapter into separate classes / extensions
> We should also provide a mechanism for the sever adapter to be stack agnostic so that we can add more stacks by just addding an extension
> This will be probably required by FUSE integration
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months