[JBoss JIRA] (JBIDE-21709) Obstacle with editing user-defined connection
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21709?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-21709.
---------------------------------
Verified in JBDS 9.1.0.CR1 B354.
> Obstacle with editing user-defined connection
> ---------------------------------------------
>
> Key: JBIDE-21709
> URL: https://issues.jboss.org/browse/JBIDE-21709
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Affects Versions: 4.3.1.Beta2
> Environment: JBDS 9.1.0.Beta2
> Reporter: Tomáš Sedmík
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
> Attachments: out.ogv
>
>
> If I create a new connection in _JMX Navigator_ and subsequently I want to edit it, I get a dialog with _The connection name is already taken_ error.
> So, no editing but, creating a new JMX connection is invoked.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBDS-3560) Arbitrary remote code execution with InvokerTransformer (COLLECTIONS-580)
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-3560?page=com.atlassian.jira.plugin.... ]
Martin Malina closed JBDS-3560.
-------------------------------
I checked once again that the updated 3.2.2 version of the jar is included in all of the relevant TPs:
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.6...
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5...
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5...
Also, I checked that in JBDS 9.1.0.CR1 B354 the correct version is included.
Closing.
> Arbitrary remote code execution with InvokerTransformer (COLLECTIONS-580)
> -------------------------------------------------------------------------
>
> Key: JBDS-3560
> URL: https://issues.jboss.org/browse/JBDS-3560
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 8.1.0.GA, 9.0.0.GA, 10.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 9.1.0.CR1, 10.0.0.Alpha1
>
> Attachments: apache-commons-collections-in-JBDS7,8,9,10.png, apache-commons-collections-in-JBDS7,8,9,10_refs1.png, apache-commons-collections-in-JBDS7,8,9,10_refs10.png, apache-commons-collections-in-JBDS7,8,9,10_refs7.png, apache-commons-collections-in-JBDS7,8,9,10_refs8-IS-fuse.png, apache-commons-collections-in-JBDS7,8,9,10_refs8.png, apache-commons-collections-in-JBDS7,8,9,10_refs9.png, orbit.R20150519210750_vs_I20151117200049.log.txt, orbit.R20150519210750_vs_I20151117200049.log_onlyLatest.txt
>
>
> This is a container issue to wrap & track https://issues.apache.org/jira/browse/COLLECTIONS-580
> Problem is that JBDS 9 (and probably 8 and 10 too) include org.apache.commons.collections 3.2.0.v2013030210310, which is affected by COLLECTIONS-580 - Arbitrary remote code execution with InvokerTransformer
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21315) CDK: Missing PATH for vagrant and VBoxManage on Mac
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21315?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-21315.
---------------------------------
Duplicate - closing.
> CDK: Missing PATH for vagrant and VBoxManage on Mac
> ---------------------------------------------------
>
> Key: JBIDE-21315
> URL: https://issues.jboss.org/browse/JBIDE-21315
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.1.CR1
>
>
> It seems there is no JIRA to track this specifically yet.
> The problem is that CDK tooling relies on PATH to find vagrant. And the "vagrant up" command in turn depends on PATH to find e.g. VBoxManage.
> On Mac, when you start your Eclipse / JBDS as an app by double-clicking an icon on your Desktop or in Finder, the Eclipse instance will have no PATH env variable.
> One workaround is to start your Eclipse from command line by going inside the package:
> {code}
> cd Eclipse.app/Contents/MacOS
> ./eclipse
> {code}
> But this is definitely not the recommended way to start Eclipse - I'm not sure if eclipse.ini is located properly in this case. But at least PATH is correct then.
> There is actually one more workaround. To add your PATH to the Environment tab in Launch config. That works for me.
> So that might be a potential solution to this problem - have a predefined PATH for each OS in case there is none defined in the Eclipse process.
> Previous related JIRAs:
> JBIDE-21175 [CDK] Require better logic to find vagrant.exe / vagrant command
> JBIDE-21172 CDK server in Starting state and cannot be stopped with wrong path to vagrant
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21293) CDK start timed out due to slow image download
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21293?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-21293.
---------------------------------
Duplicate - resolving.
> CDK start timed out due to slow image download
> ----------------------------------------------
>
> Key: JBIDE-21293
> URL: https://issues.jboss.org/browse/JBIDE-21293
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.1.CR1
>
>
> I set up a CDK server using https://github.com/redhat-developer-tooling/openshift-vagrant .
> Then I tried to start the server for the first time. Of course this will take quite long as it needs to download the VM image first. I was on a very fast connection, but it still only went around 1 MB/s. So the startup took longer than the default timeout of 450 s. The result was that the startup timed out in the middle followed by an attempted shutdown by the tooling which failed. So in the end I ended up with the running box, but with two unwanted errors.
> I'm not sure what we can do here. Perhaps just increase the timeout to something bigger? Even better would be if could detect that a download is in progress so it will take longer, but I don't think the current mechanism is capable of anything like that.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21319) CDK start fails for no reason - it's actually running
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21319?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-21319.
---------------------------------
Duplicate - closing.
> CDK start fails for no reason - it's actually running
> -----------------------------------------------------
>
> Key: JBIDE-21319
> URL: https://issues.jboss.org/browse/JBIDE-21319
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.1.CR1
>
>
> I just tried to start the CDK adapter.
> After it all started, Eclipse showed me an error window saying:
> {code}
> Server cdk-v2 CDK Server failed to start.
> {code}
> The server views shows [Stopped], but running "vagrant status" in command line shows it's running.
> I know this is not much information, but really I don't have anything else.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21677) Change branding for EAP server types
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21677?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-21677.
---------------------------------
Verified in JBDS 9.1.0.CR1 B354.
> Change branding for EAP server types
> ------------------------------------
>
> Key: JBIDE-21677
> URL: https://issues.jboss.org/browse/JBIDE-21677
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.3.1.Beta2
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
> Attachments: JBIDE-21677.png, JBIDE-21677_round_shadowman_transparent.png
>
>
> 1) Change branding for EAP small icon to shadowman. Ask Catherine
> 2) Change name to "Red Hat JBoss Enterprise Application Platform x.y"
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21616) Main tab for CDK launch configuration is not whole by default
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21616?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-21616:
---------------------------------------
[~mlabuda], can you verify this in a recent nightly build? It works fine for me, but it seems this issue was only present on Linux and/or GTK3.
> Main tab for CDK launch configuration is not whole by default
> -------------------------------------------------------------
>
> Key: JBIDE-21616
> URL: https://issues.jboss.org/browse/JBIDE-21616
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.CR1
> Environment: Fedora 22, GTK3
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
> Attachments: after.png, before.png
>
>
> In launch configuration of a CDK server adapter there are 2 tabs - Main and Environment. Upon opening of launch configuration for a CDK server adapter, Main tab is preselected but there are only Location widgets available.
> !before.png!
> After switching to Environment tab and back, Working directory and Arguments widgets become available.
> !after.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21613) NPE if click on failed CDK server
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21613?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-21613.
---------------------------------
Verified in JBDS 9.1.0.CR1 B354.
> NPE if click on failed CDK server
> ---------------------------------
>
> Key: JBIDE-21613
> URL: https://issues.jboss.org/browse/JBIDE-21613
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.CR1
> Reporter: Alexey Kazakov
> Assignee: Rob Stryker
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
>
> I ran my CDK server but it failed by timeout (it tool longer than the timeout to start the server).
> When the server finally started (I saw it in the console) I clicked on the server in the server view to "restart" it. You don't need to start/stop the server. Just click on/select the server in the view:
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.CDKDockerUtility.findDockerConnection(CDKDockerUtility.java:53)
> at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInDockerViewAfterStartupAction.adaptToViewItem(CDKActionProvider.java:111)
> at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInViewAfterStartupAction.accept(CDKActionProvider.java:188)
> at org.eclipse.wst.server.ui.internal.view.servers.AbstractServerAction.selectionChanged(AbstractServerAction.java:85)
> at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInViewAfterStartupAction.selectionChanged(CDKActionProvider.java:203)
> at org.eclipse.ui.actions.SelectionProviderAction.selectionChanged(SelectionProviderAction.java:144)
> at org.eclipse.jface.viewers.Viewer$1.run(Viewer.java:158)
> 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.Viewer.fireSelectionChanged(Viewer.java:155)
> at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2178)
> at org.eclipse.jface.viewers.StructuredViewer.setSelection(StructuredViewer.java:1717)
> at org.eclipse.jface.viewers.TreeViewer.setSelection(TreeViewer.java:1069)
> at org.eclipse.ui.navigator.CommonViewer.setSelection(CommonViewer.java:368)
> at org.eclipse.jface.viewers.Viewer.setSelection(Viewer.java:383)
> at org.eclipse.wst.server.ui.internal.cnf.ServerDecoratorsHandler$1.run(ServerDecoratorsHandler.java:58)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1132)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1023)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:157)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:651)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:595)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> 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:497)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:670)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:609)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1516)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1489)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21619) Accessing CDK server raises this exception: Problems occurred when invoking code from plug-in: "org.eclipse.jface".
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21619?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-21619.
---------------------------------
Duplicate - closing.
> Accessing CDK server raises this exception: Problems occurred when invoking code from plug-in: "org.eclipse.jface".
> -------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21619
> URL: https://issues.jboss.org/browse/JBIDE-21619
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.Beta2
> Environment: JBoss Developer Studio
> Version: 9.1.0.Beta2
> Build id: Beta2-v20160127-2213-B262
> Build date: 20160127-2213
> RHEL7
> Java 1.8
> Reporter: Len DiMaggio
> Fix For: 4.3.1.CR1
>
>
> To recreate the error:
> 1) Create a new CDL server runtime - I used CDK2, Beta4
> 2) In the server explorer, start the server, and then left click on the running server
> This message is generated:
> Problems occurred when invoking code from plug-in: "org.eclipse.jface".
> And, this exception is raised:
> java.lang.NullPointerException
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.CDKDockerUtility.findDockerConnection(CDKDockerUtility.java:53)
> at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInDockerViewAfterStartupAction.adaptToViewItem(CDKActionProvider.java:111)
> at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInViewAfterStartupAction.accept(CDKActionProvider.java:188)
> at org.eclipse.wst.server.ui.internal.view.servers.AbstractServerAction.selectionChanged(AbstractServerAction.java:85)
> at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInViewAfterStartupAction.selectionChanged(CDKActionProvider.java:203)
> at org.eclipse.ui.actions.SelectionProviderAction.selectionChanged(SelectionProviderAction.java:144)
> at org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:163)
> 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.Viewer.fireSelectionChanged(Viewer.java:160)
> at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2197)
> at org.eclipse.jface.viewers.StructuredViewer.handleSelect(StructuredViewer.java:1228)
> at org.eclipse.ui.navigator.CommonViewer.handleSelect(CommonViewer.java:461)
> at org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(StructuredViewer.java:1257)
> at org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(OpenStrategy.java:242)
> at org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:236)
> at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:408)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> 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:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> 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:497)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month