[JBoss JIRA] (JBIDE-24659) NPE in AttributeControlFactory.createControl
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24659?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-24659:
----------------------------------
Component/s: jmx
(was: server)
> NPE in AttributeControlFactory.createControl
> --------------------------------------------
>
> Key: JBIDE-24659
> URL: https://issues.jboss.org/browse/JBIDE-24659
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Affects Versions: 4.5.0.AM1
> Reporter: Aurélien Pupier
> Assignee: Rob Stryker
> Fix For: 4.5.1.AM1
>
> Attachments: image-2017-07-10-16-04-14-279.png
>
>
> {noformat}
> !ENTRY org.jboss.tools.jmx.ui 4 0 2017-07-10 16:00:20.250
> !MESSAGE Unable to retrieve value for attribute FirstExchangeFailureTimestamp
> !STACK 0
> java.lang.NullPointerException
> at org.jboss.tools.jmx.ui.internal.controls.AttributeControlFactory.createControl(AttributeControlFactory.java:127)
> at org.jboss.tools.jmx.ui.internal.editors.AttributeDetails.update(AttributeDetails.java:215)
> at org.jboss.tools.jmx.ui.internal.editors.AttributeDetails.selectionChanged(AttributeDetails.java:184)
> at org.eclipse.ui.forms.DetailsPart.lambda$0(DetailsPart.java:267)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.forms.DetailsPart.showPage(DetailsPart.java:255)
> at org.eclipse.ui.forms.DetailsPart.update(DetailsPart.java:228)
> at org.eclipse.ui.forms.DetailsPart.selectionChanged(DetailsPart.java:213)
> at org.eclipse.ui.forms.ManagedForm.fireSelectionChanged(ManagedForm.java:125)
> at org.jboss.tools.jmx.ui.internal.editors.AttributesSection$1.selectionChanged(AttributesSection.java:57)
> at org.eclipse.jface.viewers.Viewer$1.run(Viewer.java:155)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil.lambda$0(JFaceUtil.java:44)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
> at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:152)
> at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2180)
> at org.eclipse.jface.viewers.StructuredViewer.handleSelect(StructuredViewer.java:1223)
> at org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(StructuredViewer.java:1252)
> at org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(OpenStrategy.java:240)
> at org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:235)
> at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:400)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4428)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4238)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3817)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1155)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1044)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
> at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151)
> 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:653)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1499)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1472)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24884) Log an error if detected cdk registry is wrong
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24884?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-24884.
---------------------------------
I was able to verify this. With my cdk wrapper script I got a warning that the registry command returned bla bla and the field in the openshift connection edit dialog stayed empty.
I used devstudio-11.1.0.AM2-v20170911-0543-B1024-installer-standalone.jar
> Log an error if detected cdk registry is wrong
> ----------------------------------------------
>
> Key: JBIDE-24884
> URL: https://issues.jboss.org/browse/JBIDE-24884
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.5.1.AM1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.5.1.AM1
>
>
> This is a followup of JBIDE-24783.
> When minishift openshift registry is unable to return a valid registry, the tooling should log an error. JBIDE-24783 was supposed to add this thing (along with removing the default value), but I was not able to trigger the error.
> The workflow is:
> Once cdk is started in eclipse, the cdk tooling will create the openshift connection and run minishift openshift registry to figure out which registry to use. But in my testing even if this returns "bla bla", the tooling will happily accept it.
> To test this, you can use a simple minishift wrapper such as this:
> {code}
> #!/bin/bash
> case $* in
> "openshift registry")
> echo bla bla
> exit 1
> ;;
> *)
> /Users/rasp/jbossqa/cdk/cdk-3.1.0/minishift $*
> esac
> {code}
> You can also remove the "exit 1" to check what happens with zero exit code.
> In my opinion any of these should trigger an error:
> a) minishift openshift registry finishes with a non-zero code
> b) the returned string is not a valid url
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBDS-4412) DevSuite 1.4 Installer Make progress/status clearer/easier to see
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4412?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4412:
--------------------------------
Fix Version/s: 11.1.0.AM2
(was: 11.x)
> DevSuite 1.4 Installer Make progress/status clearer/easier to see
> -----------------------------------------------------------------
>
> Key: JBDS-4412
> URL: https://issues.jboss.org/browse/JBDS-4412
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Environment: DevSuite 1.4 installer, Windows 10 Pro/64
> Reporter: Robert Terzi
> Assignee: Mohit Suman
> Priority: Minor
> Labels: ui
> Fix For: 11.1.0.AM2
>
>
> The overall installation progress for DevSuite 1.4 is difficult to see. You've got to scroll back and forth through the boxes to look for the small text that indicates what's going on.
> Suggestions:
> # There should be an overall progress at the top
> # There should be some indication it is still working
> # the status text in the boxes is the same color and size as the version number and other comment text making it difficult to pick out. It's easy to miss that there is status text and that it is being updated.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBDS-4411) DevSuite 1.4 installer display required disk space
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4411?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4411:
--------------------------------
Fix Version/s: 11.1.0.AM2
(was: 11.x)
> DevSuite 1.4 installer display required disk space
> ---------------------------------------------------
>
> Key: JBDS-4411
> URL: https://issues.jboss.org/browse/JBDS-4411
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Environment: DevSuite 1.4 installer, Windows 10 Pro/64
> Reporter: Robert Terzi
> Assignee: Mohit Suman
> Priority: Minor
> Labels: ui
> Fix For: 11.1.0.AM2
>
> Attachments: install-size.png
>
>
> DevSuite 1.4 installer (online) should display the disk space requirements which should include the calculation for both the downloads and the unpacked/installed files.
> As a user,
> I would like to know the disk space required to complete the installation before starting
> so that I have an idea whether the installation can be completed successfully.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-25000) Server adapter: starting into debugging fails initially (succeeds on a latter try)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25000?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-25000 at 9/11/17 5:18 PM:
-------------------------------------------------------------------
Another item to address is the [lifenessProbe|https://docs.openshift.com/container-platform/3.3/dev_guide...] that - for the nodejs-mongo-persistent template - only relies on pinging port 8080 where the web content is delivered, but not on 5858 where debugging is reachable. Their pod(s) therefore report being ready even though the debugging facility isnt:
{code:title=nodejs-mongo-persistent-1 (replication controller)}
"livenessProbe": {
"httpGet": {
"path": "/pagecount",
"port": 8080,
"scheme": "HTTP"
},
"initialDelaySeconds": 30,
"timeoutSeconds": 3,
"periodSeconds": 10,
"successThreshold": 1,
"failureThreshold": 3
},
"readinessProbe": {
"httpGet": {
"path": "/pagecount",
"port": 8080,
"scheme": "HTTP"
},
"initialDelaySeconds": 3,
"timeoutSeconds": 3,
"periodSeconds": 10,
"successThreshold": 1,
"failureThreshold": 3
}
{code}
was (Author: adietish):
Another item to address is the [lifenessProbe|https://docs.openshift.com/container-platform/3.3/dev_guide...] that - for the nodejs-mongo-persistent - only relies on pinging port 8080 where the web content is delivered, but not on 5858 where debugging is reachable. Their pod(s) therefore report being ready even though the debugging facility isnt:
{code:title=nodejs-mongo-persistent-1 (replication controller)}
"livenessProbe": {
"httpGet": {
"path": "/pagecount",
"port": 8080,
"scheme": "HTTP"
},
"initialDelaySeconds": 30,
"timeoutSeconds": 3,
"periodSeconds": 10,
"successThreshold": 1,
"failureThreshold": 3
},
"readinessProbe": {
"httpGet": {
"path": "/pagecount",
"port": 8080,
"scheme": "HTTP"
},
"initialDelaySeconds": 3,
"timeoutSeconds": 3,
"periodSeconds": 10,
"successThreshold": 1,
"failureThreshold": 3
}
{code}
> Server adapter: starting into debugging fails initially (succeeds on a latter try)
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-25000
> URL: https://issues.jboss.org/browse/JBIDE-25000
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.5.1.AM2
>
> Attachments: failed-to-connect-v8-vm.png
>
>
> # ASSERT: have an application running in OpenShift based on the "nodejs-mongo-persistent" template
> # ASSERT: have a server adapter for it
> # EXEC/ASSERT: have the adapter started in non-debugging/normal mode
> # EXEC: restart the adapter debugging
> Result:
> !failed-to-connect-v8-vm.png!
> {code}
> java.io.IOException: Failed to get version
> at org.eclipse.wst.jsdt.chromium.internal.v8native.JavascriptVmImpl.newIOException(JavascriptVmImpl.java:114)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:132)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attach(StandaloneVmImpl.java:79)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.JavascriptVmEmbedderFactory$4$1.attach(JavascriptVmEmbedderFactory.java:207)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.DebugTargetImpl.attach(DebugTargetImpl.java:74)
> at org.eclipse.wst.jsdt.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:101)
> 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.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> Caused by: java.util.concurrent.ExecutionException: java.io.IOException: End of stream
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:206)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:127)
> ... 9 more
> Caused by: java.io.IOException: End of stream
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:127)
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:1)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl.perform(Handshaker.java:104)
> at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection$ReaderThread.run(SocketConnection.java:158)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-25000) Server adapter: starting into debugging fails initially (succeeds on a latter try)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25000?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-25000 at 9/11/17 5:17 PM:
-------------------------------------------------------------------
Another item to address is the [lifenessProbe|https://docs.openshift.com/container-platform/3.3/dev_guide...] that - for the nodejs-mongo-persistent - only relies on pinging port 8080 where the web content is delivered, but not on 5858 where debugging is reachable. Their pod(s) therefore report being ready even though the debugging facility isnt:
{code:title=nodejs-mongo-persistent-1 (replication controller)}
"livenessProbe": {
"httpGet": {
"path": "/pagecount",
"port": 8080,
"scheme": "HTTP"
},
"initialDelaySeconds": 30,
"timeoutSeconds": 3,
"periodSeconds": 10,
"successThreshold": 1,
"failureThreshold": 3
},
"readinessProbe": {
"httpGet": {
"path": "/pagecount",
"port": 8080,
"scheme": "HTTP"
},
"initialDelaySeconds": 3,
"timeoutSeconds": 3,
"periodSeconds": 10,
"successThreshold": 1,
"failureThreshold": 3
}
{code}
was (Author: adietish):
Another item to address is the [lifenessProbe|https://docs.openshift.com/container-platform/3.3/dev_guide...] that - for the nodejs-mongo-persistent - only relies on pinging port 8080 where the web content is delivered, but not on 5858 where debugging is reachable. Their pod(s) therefore report being ready even though the debugging facility isnt:
{code:title=nodejs-mongo-persistent-1 (replication controller)}
"livenessProbe" : {
"httpGet" : {
"path" : "/pagecount",
"port" : 8080,
"scheme" : "HTTP"
},
"initialDelaySeconds" : 30,
"timeoutSeconds" : 3,
"periodSeconds" : 10,
"successThreshold" : 1,
"failureThreshold" : 3
},
"readinessProbe" : {
"httpGet" : {
"path" : "/pagecount",
"port" : 8080,
"scheme" : "HTTP"
},
"initialDelaySeconds" : 3,
"timeoutSeconds" : 3,
"periodSeconds" : 10,
"successThreshold" : 1,
"failureThreshold" : 3
},
{code}
> Server adapter: starting into debugging fails initially (succeeds on a latter try)
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-25000
> URL: https://issues.jboss.org/browse/JBIDE-25000
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.5.1.AM2
>
> Attachments: failed-to-connect-v8-vm.png
>
>
> # ASSERT: have an application running in OpenShift based on the "nodejs-mongo-persistent" template
> # ASSERT: have a server adapter for it
> # EXEC/ASSERT: have the adapter started in non-debugging/normal mode
> # EXEC: restart the adapter debugging
> Result:
> !failed-to-connect-v8-vm.png!
> {code}
> java.io.IOException: Failed to get version
> at org.eclipse.wst.jsdt.chromium.internal.v8native.JavascriptVmImpl.newIOException(JavascriptVmImpl.java:114)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:132)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attach(StandaloneVmImpl.java:79)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.JavascriptVmEmbedderFactory$4$1.attach(JavascriptVmEmbedderFactory.java:207)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.DebugTargetImpl.attach(DebugTargetImpl.java:74)
> at org.eclipse.wst.jsdt.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:101)
> 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.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> Caused by: java.util.concurrent.ExecutionException: java.io.IOException: End of stream
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:206)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:127)
> ... 9 more
> Caused by: java.io.IOException: End of stream
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:127)
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:1)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl.perform(Handshaker.java:104)
> at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection$ReaderThread.run(SocketConnection.java:158)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months