[JBoss JIRA] (JBIDE-25860) CDK/Minishift Server Adapter - No monitoring port can be added
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25860?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-25860:
----------------------------------
Description: What is monitoring good for in server adapters like CDK and/or Minishift if any monitoring is not available and cannot be added? (was: Was is monitoring good for in server adapters like CDK and/or Minishift if any monitoring is not available and cannot be added?)
> CDK/Minishift Server Adapter - No monitoring port can be added
> --------------------------------------------------------------
>
> Key: JBIDE-25860
> URL: https://issues.jboss.org/browse/JBIDE-25860
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.5.3.AM3
> Reporter: Ondrej Dockal
> Assignee: Rob Stryker
> Priority: Minor
>
> What is monitoring good for in server adapters like CDK and/or Minishift if any monitoring is not available and cannot be added?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 4 months
[JBoss JIRA] (JBIDE-26311) EAP 7.1 fails to stop when connected over ssh
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26311?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-26311:
-------------------------------------
Can you please add a video of this, from a clean workspace? I'm clearly missing some steps.
> 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
> Labels: regression
> 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.5.0#75005)
7 years, 4 months
[JBoss JIRA] (JBIDE-26148) CommandLocationBinary: only searches once (wont retry if it fails, forcing me to restart Eclipse once I corrected a broken link)
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26148?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-26148:
-------------------------------------
I'd suggest a preference-page level force-refresh of that cache, rather than an automatic update.
> CommandLocationBinary: only searches once (wont retry if it fails, forcing me to restart Eclipse once I corrected a broken link)
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26148
> URL: https://issues.jboss.org/browse/JBIDE-26148
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
>
> [CommandLocationBinary|https://github.com/adietish/jbosstools-openshift/bl...] allows to lookup a command (on the $PATH, etc.). But it'll only do so once:
> {code:title=CommandLocationBinary}
> public String findLocation(int timeout) {
> if (foundLoc != null || searchFailed)
> return foundLoc;
> String searched = CommandLocationLookupStrategy.get().search(this, timeout);
> if (searched == null) {
> searchFailed = true;
> }
> foundLoc = searched;
> return searched;
> }
> {code}
> Once the lookup failed, it'll store this in the var *searchFailed* and wont do it a 2nd time.
> What if I update my ex. correct a broken link to oc while I keep Eclipse running?
> I'd think that one should be able to repeat the lookup if it fails since the user could modify it's system while he keeps Eclipse running. Afaics the current impl forces me to restart Eclipse.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 4 months
[JBoss JIRA] (JBIDE-26158) Server adapter: NPE when starting adapter into Debug
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26158?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26158:
-------------------------------------
Fix Version/s: 4.9.0.Final
(was: 4.9.0.AM3)
> Server adapter: NPE when starting adapter 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
> Labels: upstream
> Fix For: 4.9.0.Final
>
> 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.5.0#75005)
7 years, 4 months
[JBoss JIRA] (ERT-665) [GTK3] Breakpoint condition text editor has no cursor [EBZ#538590]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-665:
---------------------------------------
Summary: [GTK3] Breakpoint condition text editor has no cursor [EBZ#538590]
Key: ERT-665
URL: https://issues.jboss.org/browse/ERT-665
Project: Eclipse Release Train
Issue Type: Task
Components: Platform
Reporter: Friendly Jira Robot
Fix For: 2018-09 RC2
To reproduce:
1. Set breakpoint anywhere in Java code.
2. Edit breakpoint.
3. Enable breakpoint condition.
4. Edit the condition.
5. Observe that there is no text cursor.
Seen in:
Eclipse SDK
Version: 4.9
Build id: I20180625-1545
Not seen in:
Eclipse SDK
Version: Photon (4.8)
Build id: I20180611-0500
Seen with RHEL 7.4, GTK 3.22.10. Not seen on Windows 7.
Text cursors are relatively basic functionality and very useful when writing any sort of text. Its somewhat odd to not have one, and it really harms editing the breakpoint condition.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 4 months
[JBoss JIRA] (JBIDE-26333) CDK server adapter: errror while creating Openshift connection after start of CDK 3.6 server adapter
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26333?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26333:
-------------------------------------
Sprint: devex #154 September 2018
> CDK server adapter: errror while creating Openshift connection after start of CDK 3.6 server adapter
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26333
> URL: https://issues.jboss.org/browse/JBIDE-26333
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.9.0.AM3
> Reporter: Ondrej Dockal
> Assignee: Andre Dietisheim
> Labels: cdk_server_adapter
> Fix For: 4.9.0.AM3
>
> Attachments: CDKStartupOSconnError.gif, screenshot-1.png
>
>
> I am watching error being thrown just after cdk server adapter is created and OS untrusted ssl cert. accepted. Also, this throws an Error dialog (making itests to fail).
> {code}
> null
> org.jboss.tools.openshift.cdk.server
> Error
> Sun Sep 02 20:16:37 CEST 2018
> Error contacting OpenShift
> org.jboss.tools.openshift.internal.cdk.server.core.adapter.OpenShiftNotReadyPollingException: The CDK VM is up and running, but OpenShift is unreachable at url https://192.168.42.235:8443. The VM may not have been registered successfully. Please check your console output for more information
> at org.jboss.tools.openshift.internal.cdk.server.core.adapter.MinishiftPoller.checkOpenShiftHealth(MinishiftPoller.java:145)
> at org.jboss.tools.openshift.internal.cdk.server.core.adapter.MinishiftPoller.checkOpenShiftHealth(MinishiftPoller.java:124)
> at org.jboss.tools.openshift.internal.cdk.server.core.adapter.MinishiftPoller.onePing(MinishiftPoller.java:79)
> at org.jboss.tools.openshift.internal.cdk.server.core.adapter.AbstractCDKPoller.onePingSafe(AbstractCDKPoller.java:90)
> at org.jboss.tools.openshift.internal.cdk.server.core.adapter.AbstractCDKPoller.getCurrentStateSynchronous(AbstractCDKPoller.java:78)
> at org.jboss.tools.openshift.internal.cdk.server.core.adapter.controllers.AbstractCDKLaunchController.handleProcessTerminated(AbstractCDKLaunchController.java:232)
> at org.jboss.tools.openshift.internal.cdk.server.core.adapter.controllers.AbstractCDKLaunchController$4.run(AbstractCDKLaunchController.java:188)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 4 months
[JBoss JIRA] (JBIDE-26333) CDK server adapter: errror while creating Openshift connection after start of CDK 3.6 server adapter
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26333?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26333:
-------------------------------------
Fix Version/s: 4.9.0.AM3
(was: 4.9.0.Final)
> CDK server adapter: errror while creating Openshift connection after start of CDK 3.6 server adapter
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26333
> URL: https://issues.jboss.org/browse/JBIDE-26333
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.9.0.AM3
> Reporter: Ondrej Dockal
> Assignee: Andre Dietisheim
> Labels: cdk_server_adapter
> Fix For: 4.9.0.AM3
>
> Attachments: CDKStartupOSconnError.gif, screenshot-1.png
>
>
> I am watching error being thrown just after cdk server adapter is created and OS untrusted ssl cert. accepted. Also, this throws an Error dialog (making itests to fail).
> {code}
> null
> org.jboss.tools.openshift.cdk.server
> Error
> Sun Sep 02 20:16:37 CEST 2018
> Error contacting OpenShift
> org.jboss.tools.openshift.internal.cdk.server.core.adapter.OpenShiftNotReadyPollingException: The CDK VM is up and running, but OpenShift is unreachable at url https://192.168.42.235:8443. The VM may not have been registered successfully. Please check your console output for more information
> at org.jboss.tools.openshift.internal.cdk.server.core.adapter.MinishiftPoller.checkOpenShiftHealth(MinishiftPoller.java:145)
> at org.jboss.tools.openshift.internal.cdk.server.core.adapter.MinishiftPoller.checkOpenShiftHealth(MinishiftPoller.java:124)
> at org.jboss.tools.openshift.internal.cdk.server.core.adapter.MinishiftPoller.onePing(MinishiftPoller.java:79)
> at org.jboss.tools.openshift.internal.cdk.server.core.adapter.AbstractCDKPoller.onePingSafe(AbstractCDKPoller.java:90)
> at org.jboss.tools.openshift.internal.cdk.server.core.adapter.AbstractCDKPoller.getCurrentStateSynchronous(AbstractCDKPoller.java:78)
> at org.jboss.tools.openshift.internal.cdk.server.core.adapter.controllers.AbstractCDKLaunchController.handleProcessTerminated(AbstractCDKLaunchController.java:232)
> at org.jboss.tools.openshift.internal.cdk.server.core.adapter.controllers.AbstractCDKLaunchController$4.run(AbstractCDKLaunchController.java:188)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 4 months
[JBoss JIRA] (JBIDE-26333) CDK server adapter: errror while creating Openshift connection after start of CDK 3.6 server adapter
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26333?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-26333:
------------------------------------------
fix in client library was successfully tested against CDK 3.0.0, 3.5.0, 3.6.0.
openshift-restclient-java 6.1.2.Final that contains the fix was released to jboss maven repo: https://repository.jboss.org/nexus/service/local/repositories/releases/co...
> CDK server adapter: errror while creating Openshift connection after start of CDK 3.6 server adapter
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26333
> URL: https://issues.jboss.org/browse/JBIDE-26333
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.9.0.AM3
> Reporter: Ondrej Dockal
> Assignee: Andre Dietisheim
> Labels: cdk_server_adapter
> Fix For: 4.9.0.Final
>
> Attachments: CDKStartupOSconnError.gif, screenshot-1.png
>
>
> I am watching error being thrown just after cdk server adapter is created and OS untrusted ssl cert. accepted. Also, this throws an Error dialog (making itests to fail).
> {code}
> null
> org.jboss.tools.openshift.cdk.server
> Error
> Sun Sep 02 20:16:37 CEST 2018
> Error contacting OpenShift
> org.jboss.tools.openshift.internal.cdk.server.core.adapter.OpenShiftNotReadyPollingException: The CDK VM is up and running, but OpenShift is unreachable at url https://192.168.42.235:8443. The VM may not have been registered successfully. Please check your console output for more information
> at org.jboss.tools.openshift.internal.cdk.server.core.adapter.MinishiftPoller.checkOpenShiftHealth(MinishiftPoller.java:145)
> at org.jboss.tools.openshift.internal.cdk.server.core.adapter.MinishiftPoller.checkOpenShiftHealth(MinishiftPoller.java:124)
> at org.jboss.tools.openshift.internal.cdk.server.core.adapter.MinishiftPoller.onePing(MinishiftPoller.java:79)
> at org.jboss.tools.openshift.internal.cdk.server.core.adapter.AbstractCDKPoller.onePingSafe(AbstractCDKPoller.java:90)
> at org.jboss.tools.openshift.internal.cdk.server.core.adapter.AbstractCDKPoller.getCurrentStateSynchronous(AbstractCDKPoller.java:78)
> at org.jboss.tools.openshift.internal.cdk.server.core.adapter.controllers.AbstractCDKLaunchController.handleProcessTerminated(AbstractCDKLaunchController.java:232)
> at org.jboss.tools.openshift.internal.cdk.server.core.adapter.controllers.AbstractCDKLaunchController$4.run(AbstractCDKLaunchController.java:188)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 4 months