[JBoss JIRA] (JBIDE-26334) Launcher wizard: improve user experience
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26334?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26334:
-------------------------------------
Fix Version/s: 4.9.0.Final
> Launcher wizard: improve user experience
> ----------------------------------------
>
> Key: JBIDE-26334
> URL: https://issues.jboss.org/browse/JBIDE-26334
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.9.0.AM3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: launcher_wizard
> Fix For: 4.9.0.Final
>
> Attachments: maven-artifact-elements.png, mission-infos.png
>
>
> The launcher wizard that we implemented in 4.9.AM3 works but it lacks explanations that would help a novice user.
> Suggested improvements:
> * !mission-infos.png! A novice user has no idea what a mission is all about. We should maybe add an explanatory label that tells the user what he's picking with a mission. And then we should explain what the mission that he has chose will provide.
> * !maven-artifact-elements.png! A novice user has no idea what the maven artifact elements are for.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 4 months
[JBoss JIRA] (JBIDE-26334) Launcher wizard: improve user experience
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26334?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26334:
-------------------------------------
Labels: launcher_wizard (was: )
> Launcher wizard: improve user experience
> ----------------------------------------
>
> Key: JBIDE-26334
> URL: https://issues.jboss.org/browse/JBIDE-26334
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.9.0.AM3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: launcher_wizard
> Fix For: 4.9.0.Final
>
> Attachments: maven-artifact-elements.png, mission-infos.png
>
>
> The launcher wizard that we implemented in 4.9.AM3 works but it lacks explanations that would help a novice user.
> Suggested improvements:
> * !mission-infos.png! A novice user has no idea what a mission is all about. We should maybe add an explanatory label that tells the user what he's picking with a mission. And then we should explain what the mission that he has chose will provide.
> * !maven-artifact-elements.png! A novice user has no idea what the maven artifact elements are for.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 4 months
[JBoss JIRA] (JBIDE-26334) Launcher wizard: improve user experience
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-26334:
----------------------------------------
Summary: Launcher wizard: improve user experience
Key: JBIDE-26334
URL: https://issues.jboss.org/browse/JBIDE-26334
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.9.0.AM3
Reporter: Andre Dietisheim
Attachments: maven-artifact-elements.png, mission-infos.png
The launcher wizard that we implemented in 4.9.AM3 works but it lacks explanations that would help a novice user.
Suggested improvements:
* [^mission-infos.png] A novice user has no idea what a mission is all about. We should maybe add an explanatory label that tells the user what he's picking with a mission. And then we should explain what the mission that he has chose will provide.
* [^maven-artifact-elements.png] A novice user has no idea what the maven artifact elements are for.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 4 months
[JBoss JIRA] (JBIDE-26333) Error is thrown while creating Openshift Connection after start up of CDK server adapter
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26333?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-26333 at 9/3/18 9:20 AM:
------------------------------------------------------------------
[~odockal] this only happens to you with cdk 3.6, not 3.5, right? Asking to get to know if this is cdk 3.6 specific.
And then, do you still have the error if you check --skip-registration (possible workaround)?
was (Author: adietish):
[~odockal] this only happens to you with cdk 3.6, not 3.5, right? Asking to get to know if this is cdk 3.6 specific.
> Error is thrown while creating Openshift Connection after start up of CDK 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
> Fix For: 4.9.0.Final
>
> Attachments: CDKStartupOSconnError.gif
>
>
> 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) Error is thrown while creating Openshift Connection after start up of CDK server adapter
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26333?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-26333:
------------------------------------------
[~odockal] this only happens to you with cdk 3.6, not 3.5, right? Asking to get to know if this is cdk 3.6 specific.
> Error is thrown while creating Openshift Connection after start up of CDK 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
> Fix For: 4.9.0.Final
>
> Attachments: CDKStartupOSconnError.gif
>
>
> 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-26311) EAP 7.1 fails to stop when connected over ssh
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26311?page=com.atlassian.jira.plugi... ]
Josef Kopriva commented on JBIDE-26311:
---------------------------------------
Hi [~rob.stryker], I was able to reproduce this with devstudio AM3-v20180903-0416-B3304.
Also I have seen this error in error log(not sure, if I have wrong configuration):
{code:java}
eclipse.buildId=12.9.0.AM3-v20180903-0416-B3304
java.version=1.8.0_181
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Framework arguments: -product com.jboss.devstudio.core.product
Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
org.jboss.ide.eclipse.as.core
Error
Mon Sep 03 10:45:20 CEST 2018
Unable to retrieve a list of remote deployment scanners for server Red Hat JBoss EAP 7.1 TRe
org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: java.io.IOException: java.net.ConnectException: WFLYPRT0053: Could not connect to http-remoting://10.40.5.55:9990. The connection failed
at org.jboss.ide.eclipse.as.internal.management.wf11.WildFly11Manager.execute(WildFly11Manager.java:493)
at org.jboss.ide.eclipse.as.internal.management.wf11.WildFly11ManagerService.execute(WildFly11ManagerService.java:182)
at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.execute(JBoss7ManagerServiceProxy.java:87)
at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility$1.execute(AS7DeploymentScannerUtility.java:295)
at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility$1.execute(AS7DeploymentScannerUtility.java:1)
at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerUtil.executeWithService(JBoss7ManagerUtil.java:136)
at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility.executeWithResult(AS7DeploymentScannerUtility.java:293)
at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility.getDeploymentScanners(AS7DeploymentScannerUtility.java:164)
at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility.getDeploymentScannersBlocking(AS7DeploymentScannerUtility.java:124)
at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility.getDeploymentScannersBlocking(AS7DeploymentScannerUtility.java:114)
at org.jboss.ide.eclipse.as.ui.dialogs.ModifyDeploymentScannerIntervalDialog$DeploymentScannerUIServerStartedListener$1.run(ModifyDeploymentScannerIntervalDialog.java:82)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
Caused by: java.io.IOException: java.net.ConnectException: WFLYPRT0053: Could not connect to http-remoting://10.40.5.55:9990. The connection failed
at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:149)
at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:75)
at org.jboss.ide.eclipse.as.internal.management.wf11.WildFly11Manager.execute(WildFly11Manager.java:482)
... 11 more
Caused by: java.net.ConnectException: WFLYPRT0053: Could not connect to http-remoting://10.40.5.55:9990. The connection failed
at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:128)
at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:259)
at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
at org.jboss.as.protocol.mgmt.ManagementClientChannelStrategy$Establishing.getChannel(ManagementClientChannelStrategy.java:162)
at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:146)
at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:60)
at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:135)
at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:110)
at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:263)
at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:168)
at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147)
... 13 more
Caused by: java.net.ConnectException: Connection refused
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
at org.xnio.nio.WorkerThread$ConnectHandle.handleReady(WorkerThread.java:327)
at org.xnio.nio.WorkerThread.run(WorkerThread.java:591)
at ...asynchronous invocation...(Unknown Source)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:570)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:532)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:520)
at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:204)
at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:120)
... 23 more
{code}
> 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] (JBDS-4711) Add support for LFS via egit to Devstudio/JBoss Tools? (was ClassNotFoundException in Error Log after start: Builtin LFS support not present/detected)
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBDS-4711?page=com.atlassian.jira.plugin.... ]
Josef Kopriva closed JBDS-4711.
-------------------------------
Closing, its fixed now.
Verified in:
Red Hat Developer Studio
Version: 12.9.0.AM3
Build id: AM3-v20180903-0416-B3304
Build date: 20180903-0416
> Add support for LFS via egit to Devstudio/JBoss Tools? (was ClassNotFoundException in Error Log after start: Builtin LFS support not present/detected)
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4711
> URL: https://issues.jboss.org/browse/JBDS-4711
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, upstream
> Affects Versions: 12.0.0.GA
> Environment: F28 + 12.0.0.GA-v20180625-0632-B2859
> Reporter: Josef Kopriva
> Assignee: Josef Kopriva
> Priority: Minor
> Fix For: 12.9.0.AM3
>
>
> After every start of devstudio, there is a warning:
> {code:java}
> eclipse.buildId=12.0.0.GA-v20180625-0632-B2859
> java.version=1.8.0_172
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -data file:/home/jkopriva/devstudio_B2859_2/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.eclipse.egit.core
> Warning
> Mon Jun 25 13:18:32 CEST 2018
> Builtin LFS support not present/detected
> java.lang.ClassNotFoundException: org.eclipse.jgit.lfs.BuiltinLFS cannot be found by org.eclipse.egit.core_5.0.0.201806131550-r
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:508)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:419)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:411)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:150)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at org.eclipse.egit.core.Activator.registerBuiltinLFS(Activator.java:279)
> at org.eclipse.egit.core.Activator.start(Activator.java:212)
> at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:779)
> at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:772)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:729)
> at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:1002)
> at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:354)
> at org.eclipse.osgi.container.Module.doStart(Module.java:581)
> at org.eclipse.osgi.container.Module.start(Module.java:449)
> at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:468)
> at org.eclipse.osgi.internal.hooks.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:114)
> at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:505)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:328)
> at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:392)
> at org.eclipse.osgi.internal.loader.sources.SingleSourcePackage.loadClass(SingleSourcePackage.java:36)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:454)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:419)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:411)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:150)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at org.eclipse.egit.ui.Activator$RepositoryChangeScanner.<init>(Activator.java:921)
> at org.eclipse.egit.ui.Activator.setupRepoChangeScanner(Activator.java:1034)
> at org.eclipse.egit.ui.Activator.start(Activator.java:336)
> at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:779)
> at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:772)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:729)
> at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:1002)
> at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:354)
> at org.eclipse.osgi.container.Module.doStart(Module.java:581)
> at org.eclipse.osgi.container.Module.start(Module.java:449)
> at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:468)
> at org.eclipse.osgi.internal.hooks.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:114)
> at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:505)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:328)
> at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:392)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:470)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:419)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:411)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:150)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at org.eclipse.osgi.internal.framework.EquinoxBundle.loadClass(EquinoxBundle.java:609)
> at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:177)
> at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:931)
> at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
> at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:60)
> at org.eclipse.ui.internal.services.WorkbenchServiceRegistry.getSourceProviders(WorkbenchServiceRegistry.java:174)
> at org.eclipse.ui.internal.services.SourceProviderService.readRegistry(SourceProviderService.java:104)
> at org.eclipse.ui.internal.Workbench$34.runWithException(Workbench.java:2378)
> at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:32)
> at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:233)
> at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:144)
> at org.eclipse.swt.widgets.Display.syncExec(Display.java:5831)
> at org.eclipse.ui.internal.StartupThreading.runWithoutExceptions(StartupThreading.java:95)
> at org.eclipse.ui.internal.Workbench.initializeDefaultServices(Workbench.java:2373)
> at org.eclipse.ui.internal.Workbench.init(Workbench.java:1654)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2859)
> at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:597)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:152)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:656)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:592)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1498)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1471)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 4 months
[JBoss JIRA] (JBIDE-26333) Error is thrown while creating Openshift Connection after start up of CDK server adapter
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26333?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-26333:
----------------------------------
Fix Version/s: 4.9.0.Final
> Error is thrown while creating Openshift Connection after start up of CDK 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
> Fix For: 4.9.0.Final
>
> Attachments: CDKStartupOSconnError.gif
>
>
> 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