[JBoss JIRA] (JBIDE-22601) "Unable to choose a subsystem" error when trying to start a remote server with management
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22601?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-22601:
---------------------------------------
I verified this in devstudio-10.0.0.GA-v20160615-0653-B30-installer-standalone.jar.
I tried a remote EAP 7 with management. Both with and without a local runtime.
Then I tried a remote EAP 6.4, that also works.
Just to be sure, I also tried some local servers.
So this all works, but unfortunately there is one case where it sometimes doesn't work:
Remote server with FS operations sometimes fails to stop: JBIDE-22605 .
> "Unable to choose a subsystem" error when trying to start a remote server with management
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-22601
> URL: https://issues.jboss.org/browse/JBIDE-22601
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.0.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: respin-b
> Fix For: 4.4.0.Final
>
>
> When you set up a remote EAP 6 or 7 server and then try to run it, you get this error:
> Unable to choose a subsystem. Multiple subsystems found for servertype org.jboss.ide.eclipse.as.eap.61 and system type deploymentOptions
> Note: This bug happens with management mode, not with filesystem operations
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (ERT-305) Unable to open the Registry preference pages [EBZ#496160]
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/ERT-305?page=com.atlassian.jira.plugin.sy... ]
Xavier Coulon resolved ERT-305.
-------------------------------
Fix Version/s: Neon (4.6)
Assignee: Xavier Coulon
Resolution: Done
Closing as this was already fixed in commit 146087222ac3db744ca9537e5e72fc7c2a3d8add.
> Unable to open the Registry preference pages [EBZ#496160]
> ---------------------------------------------------------
>
> Key: ERT-305
> URL: https://issues.jboss.org/browse/ERT-305
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Linux Tools
> Reporter: Friendly Jira Robot
> Assignee: Xavier Coulon
> Labels: Docker, bzira
> Fix For: Neon (4.6)
>
>
> Here's the error I get, using the clean workspace:
> java.lang.ArrayIndexOutOfBoundsException: 1
> at org.eclipse.linuxtools.internal.docker.core.RegistryAccountManager.getAccounts(RegistryAccountManager.java:43)
> at org.eclipse.linuxtools.internal.docker.ui.preferences.DockerRegistryAccountPreferencePage.init(DockerRegistryAccountPreferencePage.java:260)
> at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceNode.createPage(WorkbenchPreferenceNode.java:58)
> at org.eclipse.jface.preference.PreferenceDialog.createPage(PreferenceDialog.java:1280)
> at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.createPage(FilteredPreferenceDialog.java:355)
> at org.eclipse.jface.preference.PreferenceDialog.showPage(PreferenceDialog.java:1167)
> at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.showPage(FilteredPreferenceDialog.java:608)
> at org.eclipse.jface.preference.PreferenceDialog$5.lambda$0(PreferenceDialog.java:656)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.jface.preference.PreferenceDialog$5.selectionChanged(PreferenceDialog.java:653)
> at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:878)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
> at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:875)
> at org.eclipse.jface.viewers.StructuredViewer.handlePostSelect(StructuredViewer.java:1244)
> at org.eclipse.jface.viewers.StructuredViewer$5.widgetSelected(StructuredViewer.java:1270)
> at org.eclipse.jface.util.OpenStrategy.firePostSelectionEvent(OpenStrategy.java:265)
> at org.eclipse.jface.util.OpenStrategy.access$5(OpenStrategy.java:259)
> at org.eclipse.jface.util.OpenStrategy$1.lambda$1(OpenStrategy.java:431)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4024)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3700)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
> at org.eclipse.jface.window.Window.open(Window.java:794)
> at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:211)
> at org.eclipse.ui.internal.handlers.ShowPreferencePageHandler.execute(ShowPreferencePageHandler.java:59)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> at sun.reflect.GeneratedMethodAccessor107.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:54)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:282)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:264)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:494)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:488)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:196)
> at org.eclipse.e4.ui.workbench.renderers.swt.cocoa.CocoaUIHandler.runCommand(CocoaUIHandler.java:647)
> at org.eclipse.e4.ui.workbench.renderers.swt.cocoa.CocoaUIHandler.access$5(CocoaUIHandler.java:634)
> at org.eclipse.e4.ui.workbench.renderers.swt.cocoa.CocoaUIHandler$3.widgetSelected(CocoaUIHandler.java:506)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4248)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1501)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1524)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1509)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1313)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4072)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1119)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1020)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> 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:673)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (ERT-305) Unable to open the Registry preference pages [EBZ#496160]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-305:
---------------------------------------
Summary: Unable to open the Registry preference pages [EBZ#496160]
Key: ERT-305
URL: https://issues.jboss.org/browse/ERT-305
Project: Eclipse Release Train
Issue Type: Task
Components: Linux Tools
Reporter: Friendly Jira Robot
Here's the error I get, using the clean workspace:
java.lang.ArrayIndexOutOfBoundsException: 1
at org.eclipse.linuxtools.internal.docker.core.RegistryAccountManager.getAccounts(RegistryAccountManager.java:43)
at org.eclipse.linuxtools.internal.docker.ui.preferences.DockerRegistryAccountPreferencePage.init(DockerRegistryAccountPreferencePage.java:260)
at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceNode.createPage(WorkbenchPreferenceNode.java:58)
at org.eclipse.jface.preference.PreferenceDialog.createPage(PreferenceDialog.java:1280)
at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.createPage(FilteredPreferenceDialog.java:355)
at org.eclipse.jface.preference.PreferenceDialog.showPage(PreferenceDialog.java:1167)
at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.showPage(FilteredPreferenceDialog.java:608)
at org.eclipse.jface.preference.PreferenceDialog$5.lambda$0(PreferenceDialog.java:656)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.jface.preference.PreferenceDialog$5.selectionChanged(PreferenceDialog.java:653)
at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:878)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:875)
at org.eclipse.jface.viewers.StructuredViewer.handlePostSelect(StructuredViewer.java:1244)
at org.eclipse.jface.viewers.StructuredViewer$5.widgetSelected(StructuredViewer.java:1270)
at org.eclipse.jface.util.OpenStrategy.firePostSelectionEvent(OpenStrategy.java:265)
at org.eclipse.jface.util.OpenStrategy.access$5(OpenStrategy.java:259)
at org.eclipse.jface.util.OpenStrategy$1.lambda$1(OpenStrategy.java:431)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4024)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3700)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
at org.eclipse.jface.window.Window.open(Window.java:794)
at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:211)
at org.eclipse.ui.internal.handlers.ShowPreferencePageHandler.execute(ShowPreferencePageHandler.java:59)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
at sun.reflect.GeneratedMethodAccessor107.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:54)
at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:282)
at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:264)
at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:494)
at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:488)
at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:196)
at org.eclipse.e4.ui.workbench.renderers.swt.cocoa.CocoaUIHandler.runCommand(CocoaUIHandler.java:647)
at org.eclipse.e4.ui.workbench.renderers.swt.cocoa.CocoaUIHandler.access$5(CocoaUIHandler.java:634)
at org.eclipse.e4.ui.workbench.renderers.swt.cocoa.CocoaUIHandler$3.widgetSelected(CocoaUIHandler.java:506)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4248)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1501)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1524)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1509)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1313)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4072)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1119)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1020)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
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:673)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22605) Remote server with fs operations sometimes cannot be stopped
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22605?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-22605:
---------------------------------------
For the first several attempts, deployment worked fine. But now when I deploy the project, strange thing happens:
It will say:
{code}11:56:06,843 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found jboss-as-kitchensink-html5-mobile.war in deployment directory. To trigger deployment create a file called jboss-as-kitchensink-html5-mobile.war.dodeploy
{code}
And nothing more.
And on the server in the deployments directory, there is this:
{code}
jboss-as-kitchensink-html5-mobile.war
jboss-as-kitchensink-html5-mobile.war.undeployed
{code}
When just before the publish, there was nothing at all.
If I undeploy in the Servers view, the .undeployed marker will stay there. Now when I deploy again, it will finally be deployed. And I have these:
{code}
jboss-as-kitchensink-html5-mobile.war
jboss-as-kitchensink-html5-mobile.war.deployed
{code}
Now I undeploy and I still have this:
{code}
jboss-as-kitchensink-html5-mobile.war.undeployed
{code}
And now the server stop fails. So I killed the process.
Another attempt now:
First I removed the remaining .undeployed marker.
Then I started the server.
Then I deployed something. Again, it copied over the content, but the console only said:
{code}
12:01:39,590 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found jboss-as-kitchensink-html5-mobile.war in deployment directory. To trigger deployment create a file called jboss-as-kitchensink-html5-mobile.war.dodeploy
{code}
The dir only contains the war now:
{code}jboss-as-kitchensink-html5-mobile.war{code}
This time, I use Full Publish on the module. Now it's deployed.
The dir has this:
{code}
jboss-as-kitchensink-html5-mobile.war
jboss-as-kitchensink-html5-mobile.war.deployed
{code}
Now I undeploy. There is still the .undeployed marker.
And now server stop works. Strange? Yes.
> Remote server with fs operations sometimes cannot be stopped
> ------------------------------------------------------------
>
> Key: JBIDE-22605
> URL: https://issues.jboss.org/browse/JBIDE-22605
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.0.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
>
> Yesterday when we were found out that remote servers don't work with management operations (JBIDE-22601) I wanted to check if at least FS operations work.
> In one instance of Eclipse, stopping such server didn't work.
> But then I tried in devstudio and it worked, so I assumed it was some glitch.
> But today this happened to me again with the latest devstudio 10.0.0.GA B30 build - the one that contains a fix to the above mentioned JIRA.
> From several attempts, it seems that this is only reproducible if you deploy a project. If you just start the server and then stop, it will stop just fine.
> One more thing, regardless of whether a given server can be stopped or not, I always get this in the Error Log view during server startup:
> {code}Unable to retrieve a list of remote deployment scanners for server Red Hat JBoss EAP 7.0 marvin{code}
> (Let me know if you want an additional JIRA for that.)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22115) Connection wizard: Truncated error message display connecting to server
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22115?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-22115:
------------------------------------
Manage to reproduce with a non trusted certificate as it generate a long error message (Could not get resource ~ in namespace : javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target) due to the chain of exceptions. I fixed it by removing the first part as error message is 2 line by design and resizing for such an error message would lead to a non nice to see dialog. Upstream way of handling it was to display a tooltip with the full message content. Maybe requesting a configurable multi-line message should be a better option for upstream
> Connection wizard: Truncated error message display connecting to server
> -----------------------------------------------------------------------
>
> Key: JBIDE-22115
> URL: https://issues.jboss.org/browse/JBIDE-22115
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Final
> Environment: Version: 9.1.0.GA
> Build id: GA-v20160403-1700-B477
> Build date: 20160403-1700
> Reporter: Len DiMaggio
> Assignee: Jeff MAURY
> Priority: Minor
> Labels: connection_wizard, openshift_v3
> Fix For: 4.4.x
>
> Attachments: bad_token_1.png, bad_token_2.png
>
>
> See attached screenshot - the error message is truncated until the user expands the width of the dialog.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22605) Remote server with fs operations sometimes cannot be stopped
by Martin Malina (JIRA)
Martin Malina created JBIDE-22605:
-------------------------------------
Summary: Remote server with fs operations sometimes cannot be stopped
Key: JBIDE-22605
URL: https://issues.jboss.org/browse/JBIDE-22605
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.4.0.Final
Reporter: Martin Malina
Assignee: Rob Stryker
Yesterday when we were found out that remote servers don't work with management operations (JBIDE-22601) I wanted to check if at least FS operations work.
In one instance of Eclipse, stopping such server didn't work.
But then I tried in devstudio and it worked, so I assumed it was some glitch.
But today this happened to me again with the latest devstudio 10.0.0.GA B30 build - the one that contains a fix to the above mentioned JIRA.
>From several attempts, it seems that this is only reproducible if you deploy a project. If you just start the server and then stop, it will stop just fine.
One more thing, regardless of whether a given server can be stopped or not, I always get this in the Error Log view during server startup:
{code}Unable to retrieve a list of remote deployment scanners for server Red Hat JBoss EAP 7.0 marvin{code}
(Let me know if you want an additional JIRA for that.)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-21290) CDK 2 is detected as version 1.0
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21290?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-21290:
---------------------------------------
[~hardy.ferentschik], having this new feature in service-manager is nice, but I don't think it can help us - typically when you add the cdk in Eclipse, you will want to start it from Eclipse, so it's not running yet.
{quote}
1. The cdk.zip which maybe could be used to add it, might go away in the near future. At least that is the plan. It would be really up to the platform installers to create the marker files and add the version.
{quote}
Even if cdk.zip goes away, there will always be some folder somewhere that contains the Vagrantfile. And we just need to make sure that folder contains the marker - that should always be doable.
{quote}
2. The user could install a CDK and then upgrade it later (just the VM, not the whole install). The reported version would still be the one in the marker file.
{quote}
OK, that is a valid concern. Currently we don't support any upgrade of cdk at all, so I'm not sure exactly how that would work.
> CDK 2 is detected as version 1.0
> --------------------------------
>
> Key: JBIDE-21290
> URL: https://issues.jboss.org/browse/JBIDE-21290
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, runtime-detection, upstream
> Affects Versions: 4.3.1.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.4.x
>
> Attachments: cdk-runtime-detection.png, Screenshot 2016-01-07 09.16.12.png
>
>
> When you detect CDK using runtime detection, it will show you the name cdk-v2 which clearly shows it's version 2 (this is actually just based on the folder it seems). But the Version column says Version 1.0.
> !cdk-runtime-detection.png!
> Could we change it to version 2?
> I know that this probably doesn't have any meaning right now - I noticed there is no runtime anymore, so the version is nowhere to be seen once you create the cdk server adapter. But it would still be nicer to show the correct version if possible.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22604) CDK server adapter stuck at starting
by Jan Richter (JIRA)
Jan Richter created JBIDE-22604:
-----------------------------------
Summary: CDK server adapter stuck at starting
Key: JBIDE-22604
URL: https://issues.jboss.org/browse/JBIDE-22604
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdk
Affects Versions: 4.4.0.Final
Environment: development-suite-1.0.0-GA-20160615-188-bundle-installer.exe
devstudio 10.0.0.GA-a
CDK 2.1.RC3
Reporter: Jan Richter
I have installed the development suite using the all-in-1 installer (on 3 different windows machines now). Every time I try to start CDK using the server adapter it gets stuck on 'starting'.
In fact the CDK does start up, openshift is running, but no connection is created + the server adapter is marked as starting and the job (starting CDK) is spinning until it hits the timeout.
Strange thing is - stopping the job/server adapter at this point will first create the desired openshift connection and then CDK wil stop.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months