[JBoss JIRA] (JBIDE-24965) Server adapter: fails to "Restart in Debug"
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24965?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24965:
-------------------------------------
Affects Version/s: 4.5.1.AM2
(was: 4.5.0.AM2)
> Server adapter: fails to "Restart in Debug"
> -------------------------------------------
>
> Key: JBIDE-24965
> URL: https://issues.jboss.org/browse/JBIDE-24965
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.1.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.5.1.AM3
>
> Attachments: image-2017-09-02-01-06-58-751.png
>
>
> steps:
> # EXEC: Create a nodejs-mongo-persistent application
> # EXEC/ASSERT: Create a server adapter for the service nodejs-mongo-persistent
> # EXEC: start the server adapter via "Debug"
> # ASSERT: debugging works
> # EXEC: restart the server adapter via "Restart in Debug"
> Result:
> Debugging fails, you get the following error:
> !image-2017-09-02-01-06-58-751.png!
> In the log you find the following entry:
> {code}
> org.eclipse.core.runtime.CoreException: Could not find running pod to forward to in server adapter "nodejs-mongo-persistent (Service) at OpenShift 3 (192.168.64.2)"
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.mapPortForwarding(OpenShiftLaunchController.java:357)
> at org.jboss.tools.openshift.js.server.behaviour.OpenShiftNodejsLaunchController.access$0(OpenShiftNodejsLaunchController.java:1)
> at org.jboss.tools.openshift.js.server.behaviour.OpenShiftNodejsLaunchController$1.onDebugChange(OpenShiftNodejsLaunchController.java:83)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:221)
> at org.jboss.tools.openshift.js.server.behaviour.OpenShiftNodejsLaunchController.launch(OpenShiftNodejsLaunchController.java:52)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> 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.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> !SUBENTRY 1 org.jboss.tools.openshift.core 4 0 2017-09-02 00:32:34.031
> !MESSAGE Could not find running pod to forward to in server adapter "nodejs-mongo-persistent (Service) at OpenShift 3 (192.168.64.2)"
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24965) Server adapter: fails to "Restart in Debug"
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24965?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24965:
-------------------------------------
Fix Version/s: 4.5.1.AM3
(was: 4.5.1.AM2)
> Server adapter: fails to "Restart in Debug"
> -------------------------------------------
>
> Key: JBIDE-24965
> URL: https://issues.jboss.org/browse/JBIDE-24965
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.1.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.5.1.AM3
>
> Attachments: image-2017-09-02-01-06-58-751.png
>
>
> steps:
> # EXEC: Create a nodejs-mongo-persistent application
> # EXEC/ASSERT: Create a server adapter for the service nodejs-mongo-persistent
> # EXEC: start the server adapter via "Debug"
> # ASSERT: debugging works
> # EXEC: restart the server adapter via "Restart in Debug"
> Result:
> Debugging fails, you get the following error:
> !image-2017-09-02-01-06-58-751.png!
> In the log you find the following entry:
> {code}
> org.eclipse.core.runtime.CoreException: Could not find running pod to forward to in server adapter "nodejs-mongo-persistent (Service) at OpenShift 3 (192.168.64.2)"
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.mapPortForwarding(OpenShiftLaunchController.java:357)
> at org.jboss.tools.openshift.js.server.behaviour.OpenShiftNodejsLaunchController.access$0(OpenShiftNodejsLaunchController.java:1)
> at org.jboss.tools.openshift.js.server.behaviour.OpenShiftNodejsLaunchController$1.onDebugChange(OpenShiftNodejsLaunchController.java:83)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:221)
> at org.jboss.tools.openshift.js.server.behaviour.OpenShiftNodejsLaunchController.launch(OpenShiftNodejsLaunchController.java:52)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> 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.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> !SUBENTRY 1 org.jboss.tools.openshift.core 4 0 2017-09-02 00:32:34.031
> !MESSAGE Could not find running pod to forward to in server adapter "nodejs-mongo-persistent (Service) at OpenShift 3 (192.168.64.2)"
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24965) Server adapter: fails to "Restart in Debug"
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24965?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24965:
-------------------------------------
Labels: openshift_v3 server_adapter (was: )
> Server adapter: fails to "Restart in Debug"
> -------------------------------------------
>
> Key: JBIDE-24965
> URL: https://issues.jboss.org/browse/JBIDE-24965
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Andre Dietisheim
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.5.1.AM2
>
> Attachments: image-2017-09-02-01-06-58-751.png
>
>
> steps:
> # EXEC: Create a nodejs-mongo-persistent application
> # EXEC/ASSERT: Create a server adapter for the service nodejs-mongo-persistent
> # EXEC: start the server adapter via "Debug"
> # ASSERT: debugging works
> # EXEC: restart the server adapter via "Restart in Debug"
> Result:
> Debugging fails, you get the following error:
> !image-2017-09-02-01-06-58-751.png!
> In the log you find the following entry:
> {code}
> org.eclipse.core.runtime.CoreException: Could not find running pod to forward to in server adapter "nodejs-mongo-persistent (Service) at OpenShift 3 (192.168.64.2)"
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.mapPortForwarding(OpenShiftLaunchController.java:357)
> at org.jboss.tools.openshift.js.server.behaviour.OpenShiftNodejsLaunchController.access$0(OpenShiftNodejsLaunchController.java:1)
> at org.jboss.tools.openshift.js.server.behaviour.OpenShiftNodejsLaunchController$1.onDebugChange(OpenShiftNodejsLaunchController.java:83)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:221)
> at org.jboss.tools.openshift.js.server.behaviour.OpenShiftNodejsLaunchController.launch(OpenShiftNodejsLaunchController.java:52)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> 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.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> !SUBENTRY 1 org.jboss.tools.openshift.core 4 0 2017-09-02 00:32:34.031
> !MESSAGE Could not find running pod to forward to in server adapter "nodejs-mongo-persistent (Service) at OpenShift 3 (192.168.64.2)"
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24965) Server adapter: fails to "Restart in Debug"
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24965?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-24965:
----------------------------------------
Assignee: Andre Dietisheim
> Server adapter: fails to "Restart in Debug"
> -------------------------------------------
>
> Key: JBIDE-24965
> URL: https://issues.jboss.org/browse/JBIDE-24965
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.5.1.AM2
>
> Attachments: image-2017-09-02-01-06-58-751.png
>
>
> steps:
> # EXEC: Create a nodejs-mongo-persistent application
> # EXEC/ASSERT: Create a server adapter for the service nodejs-mongo-persistent
> # EXEC: start the server adapter via "Debug"
> # ASSERT: debugging works
> # EXEC: restart the server adapter via "Restart in Debug"
> Result:
> Debugging fails, you get the following error:
> !image-2017-09-02-01-06-58-751.png!
> In the log you find the following entry:
> {code}
> org.eclipse.core.runtime.CoreException: Could not find running pod to forward to in server adapter "nodejs-mongo-persistent (Service) at OpenShift 3 (192.168.64.2)"
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.mapPortForwarding(OpenShiftLaunchController.java:357)
> at org.jboss.tools.openshift.js.server.behaviour.OpenShiftNodejsLaunchController.access$0(OpenShiftNodejsLaunchController.java:1)
> at org.jboss.tools.openshift.js.server.behaviour.OpenShiftNodejsLaunchController$1.onDebugChange(OpenShiftNodejsLaunchController.java:83)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:221)
> at org.jboss.tools.openshift.js.server.behaviour.OpenShiftNodejsLaunchController.launch(OpenShiftNodejsLaunchController.java:52)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> 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.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> !SUBENTRY 1 org.jboss.tools.openshift.core 4 0 2017-09-02 00:32:34.031
> !MESSAGE Could not find running pod to forward to in server adapter "nodejs-mongo-persistent (Service) at OpenShift 3 (192.168.64.2)"
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24965) Server adapter: fails to "Restart in Debug"
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24965?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24965:
-------------------------------------
Fix Version/s: 4.5.1.AM2
> Server adapter: fails to "Restart in Debug"
> -------------------------------------------
>
> Key: JBIDE-24965
> URL: https://issues.jboss.org/browse/JBIDE-24965
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.5.1.AM2
>
> Attachments: image-2017-09-02-01-06-58-751.png
>
>
> steps:
> # EXEC: Create a nodejs-mongo-persistent application
> # EXEC/ASSERT: Create a server adapter for the service nodejs-mongo-persistent
> # EXEC: start the server adapter via "Debug"
> # ASSERT: debugging works
> # EXEC: restart the server adapter via "Restart in Debug"
> Result:
> Debugging fails, you get the following error:
> !image-2017-09-02-01-06-58-751.png!
> In the log you find the following entry:
> {code}
> org.eclipse.core.runtime.CoreException: Could not find running pod to forward to in server adapter "nodejs-mongo-persistent (Service) at OpenShift 3 (192.168.64.2)"
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.mapPortForwarding(OpenShiftLaunchController.java:357)
> at org.jboss.tools.openshift.js.server.behaviour.OpenShiftNodejsLaunchController.access$0(OpenShiftNodejsLaunchController.java:1)
> at org.jboss.tools.openshift.js.server.behaviour.OpenShiftNodejsLaunchController$1.onDebugChange(OpenShiftNodejsLaunchController.java:83)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:221)
> at org.jboss.tools.openshift.js.server.behaviour.OpenShiftNodejsLaunchController.launch(OpenShiftNodejsLaunchController.java:52)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> 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.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> !SUBENTRY 1 org.jboss.tools.openshift.core 4 0 2017-09-02 00:32:34.031
> !MESSAGE Could not find running pod to forward to in server adapter "nodejs-mongo-persistent (Service) at OpenShift 3 (192.168.64.2)"
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-22544) Redudant error report in Devstudio's Problems View
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22544?page=com.atlassian.jira.plugi... ]
Victor Rubezhny commented on JBIDE-22544:
-----------------------------------------
I've changed the fix version in order to not be reported as an issue with Illegal fix version
> Redudant error report in Devstudio's Problems View
> --------------------------------------------------
>
> Key: JBIDE-22544
> URL: https://issues.jboss.org/browse/JBIDE-22544
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: javascript, upstream
> Reporter: Ondrej Dockal
> Assignee: Victor Rubezhny
> Fix For: 4.5.1.AM1
>
> Attachments: org.jboss.tools.batch.ui.bot.test.editor.design.DesignChunkStepElementTest.createStep(7).png
>
>
> Some test fails on checking number of errors in Problems View in devstudio. There are duplicated error reports.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBDS-3871) installer credentials misleading/incomplete information.
by Mohit Suman (JIRA)
[ https://issues.jboss.org/browse/JBDS-3871?page=com.atlassian.jira.plugin.... ]
Mohit Suman commented on JBDS-3871:
-----------------------------------
[~dgolovin] Should we go ahead with this JIRA as implement mentioned in the description.
As mentioned in point 2: The register link leads to register page only.
> installer credentials misleading/incomplete information.
> --------------------------------------------------------
>
> Key: JBDS-3871
> URL: https://issues.jboss.org/browse/JBDS-3871
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.Beta1
> Environment: Win 7/64 bit
> Reporter: Robert Terzi
> Assignee: Denis Golovin
> Priority: Minor
> Labels: ui
> Fix For: 11.x
>
>
> There are several problems a with the information on the platform installer's login screen:
> # "Your developers.redhat.com credentials" is misleading, Should probably be "Your Red Hat username" to be consistent with RHDeveloper registration process.
> # The register link points to the login page, not the register page.
> # Registering on RHDevelopers isn't sufficient. (A registered user gets " Terms and Conditions for CDK have not been signed."
> # There should probably be a link to a page on RHDev with more info/FAQ about credentials, the registration process, and obtaining a (no-cost) subscription.
> The platform installer description of the credentials to use are misleading. Currently it says " Try it now by providing your developers.redhat.com credentials to get access."
> Users can log into RHDevelopers via other accounts (github, linkedin, stack overflow, etc. using OAUTH). They can not log into access.redhat.com (the customer portal) or other Red Hat sites with their developer.redhat.com "credentials".
> During registration on RHDevelopers, a simple developers account is created. (Note: At this point, a Red Hat username hasn't been created yet.
> Currently, when the user clicks a download link that goes through RHDev download manager, their account is "upgraded", which creates a Red Hat user than can be used to log into RHCP. Terms & conditions are presented. A no-cost RHEL Developer suite subscription is added to the user's Red Hat account.
> Their Red Hat username and password which could be different from the RHDeveloper credentials. They will need their Red Hat username for the CDK box to attach to their subscription. Without it the CDK box won't start up correctly as it can't download software.
> Some of this is covered for external users in the No-cost RHEL Dev. Suite FAQ. http://developers.redhat.com/articles/no-cost-rhel-faq/ We might need to do a version of that for CDK and JBDS platform installer..
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months