[JBoss JIRA] (JBIDE-22686) Can't push image to docker registry
by Hardy Ferentschik (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22686?page=com.atlassian.jira.plugi... ]
Hardy Ferentschik commented on JBIDE-22686:
-------------------------------------------
{quote}
But the thing is that sometimes i needed to `vagrant provision` to start working with OS. For some reason it didn't start on it's own.
{quote}
That should not have been required. See whether it happens again. Maybe we can investigate then?
> Can't push image to docker registry
> -----------------------------------
>
> Key: JBIDE-22686
> URL: https://issues.jboss.org/browse/JBIDE-22686
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: docker, openshift
> Affects Versions: 4.4.0.Final
> Environment: Fedora 23
> Reporter: Dmitry Bocharov
> Assignee: Dmitry Bocharov
> Fix For: 4.4.x
>
> Attachments: DeployDockerImageToOS.webm, DeployedSuccessfully.webm
>
>
> The screencast of the last steps is attached.
> Properties and settings of the cdk haven't been changed. Everything is dowloaded and installed in a usual way.
> Possibly something is with the dns - maybe it wasn't configured correctly while cdk installation. Because we to push to the valid url, while OS connection only an IP in its settings.
> _exception:_
> org.eclipse.linuxtools.docker.core.DockerException: com.spotify.docker.client.DockerException: org.eclipse.linuxtools.docker.core.DockerImagePushFailedException: Image push failed: hub.openshift.rhel-cdk.10.1.2.2.xip.io/sample-project/aloha: unable to ping registry endpoint https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v0/
> v2 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v2/: dial tcp 10.1.2.2:443: connection refused
> v1 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v1/_ping: dial tcp 10.1.2.2:443: connection refused
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.pushImage(DockerConnection.java:1047)
> at org.jboss.tools.openshift.internal.ui.dockerutils.PushImageToRegistryJob.doRun(PushImageToRegistryJob.java:67)
> at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:37)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: com.spotify.docker.client.DockerException: org.eclipse.linuxtools.docker.core.DockerImagePushFailedException: Image push failed: hub.openshift.rhel-cdk.10.1.2.2.xip.io/sample-project/aloha: unable to ping registry endpoint https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v0/
> v2 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v2/: dial tcp 10.1.2.2:443: connection refused
> v1 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v1/_ping: dial tcp 10.1.2.2:443: connection refused
> at org.eclipse.linuxtools.internal.docker.core.DockerProgressHandler.progress(DockerProgressHandler.java:42)
> at com.spotify.docker.client.ProgressStream.tail(ProgressStream.java:74)
> at com.spotify.docker.client.DefaultDockerClient.push(DefaultDockerClient.java:821)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.pushImage(DockerConnection.java:1043)
> ... 3 more
> Caused by: org.eclipse.linuxtools.docker.core.DockerImagePushFailedException: Image push failed: hub.openshift.rhel-cdk.10.1.2.2.xip.io/sample-project/aloha: unable to ping registry endpoint https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v0/
> v2 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v2/: dial tcp 10.1.2.2:443: connection refused
> v1 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v1/_ping: dial tcp 10.1.2.2:443: connection refused
> at org.eclipse.linuxtools.internal.docker.ui.views.ImagePushProgressHandler.processMessage(ImagePushProgressHandler.java:49)
> at org.eclipse.linuxtools.internal.docker.core.DockerProgressHandler.progress(DockerProgressHandler.java:40)
> ... 6 more
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22603) Sometimes multiple OpenShift watch managers are periodically created and finished
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22603?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-22603:
---------------------------------------
Raising to blocker for this sprint. I am unable to perform several actions with OpenShift 3 applications because of blocking jobs and everlasting loops of watch managers.
> Sometimes multiple OpenShift watch managers are periodically created and finished
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-22603
> URL: https://issues.jboss.org/browse/JBIDE-22603
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Priority: Blocker
> Labels: explorer, openshift_v3
> Fix For: 4.4.x
>
> Attachments: watchers.png
>
>
> Sometimes when I am working with OpenShift toolings, there are created multiple OpenShift Watch Managers which are getting finished, disappearing from Progress view and another new ones are created and this repeats nonstop. Sometimes there are 2-3 running, sometimes even more. I am working with openshift-dev user, where is visible default project (still, until patch in upstream get effect) and my own project with application created from eap 6.4 basic s2i template.
> !watchers.png!
> It would not be a problem but I have a hunch it is the problem breaking automatic update of OpenShift explorer view to reflect current state and existence of resources on OpenShift server. E.g. under a service there is build table visible all the time and no application pod is shown, even build is finished and there is an application pod running on OpenShift. Another example when it is not working is when I am scaling application up/down - it does not reflect real amount of application pods.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22603) Sometimes multiple OpenShift watch managers are periodically created and finished
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22603?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-22603:
----------------------------------
Priority: Blocker (was: Critical)
> Sometimes multiple OpenShift watch managers are periodically created and finished
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-22603
> URL: https://issues.jboss.org/browse/JBIDE-22603
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Priority: Blocker
> Labels: explorer, openshift_v3
> Fix For: 4.4.x
>
> Attachments: watchers.png
>
>
> Sometimes when I am working with OpenShift toolings, there are created multiple OpenShift Watch Managers which are getting finished, disappearing from Progress view and another new ones are created and this repeats nonstop. Sometimes there are 2-3 running, sometimes even more. I am working with openshift-dev user, where is visible default project (still, until patch in upstream get effect) and my own project with application created from eap 6.4 basic s2i template.
> !watchers.png!
> It would not be a problem but I have a hunch it is the problem breaking automatic update of OpenShift explorer view to reflect current state and existence of resources on OpenShift server. E.g. under a service there is build table visible all the time and no application pod is shown, even build is finished and there is an application pod running on OpenShift. Another example when it is not working is when I am scaling application up/down - it does not reflect real amount of application pods.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22686) Can't push image to docker registry
by Dmitry Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22686?page=com.atlassian.jira.plugi... ]
Dmitry Bocharov commented on JBIDE-22686:
-----------------------------------------
Hardy, thank you! Unfortunately, can say nothing about the logs =(. But the thing is that sometimes i needed to `vagrant provision` to start working with OS. For some reason it didn't start on it's own.
> Can't push image to docker registry
> -----------------------------------
>
> Key: JBIDE-22686
> URL: https://issues.jboss.org/browse/JBIDE-22686
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: docker, openshift
> Affects Versions: 4.4.0.Final
> Environment: Fedora 23
> Reporter: Dmitry Bocharov
> Assignee: Dmitry Bocharov
> Fix For: 4.4.x
>
> Attachments: DeployDockerImageToOS.webm, DeployedSuccessfully.webm
>
>
> The screencast of the last steps is attached.
> Properties and settings of the cdk haven't been changed. Everything is dowloaded and installed in a usual way.
> Possibly something is with the dns - maybe it wasn't configured correctly while cdk installation. Because we to push to the valid url, while OS connection only an IP in its settings.
> _exception:_
> org.eclipse.linuxtools.docker.core.DockerException: com.spotify.docker.client.DockerException: org.eclipse.linuxtools.docker.core.DockerImagePushFailedException: Image push failed: hub.openshift.rhel-cdk.10.1.2.2.xip.io/sample-project/aloha: unable to ping registry endpoint https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v0/
> v2 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v2/: dial tcp 10.1.2.2:443: connection refused
> v1 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v1/_ping: dial tcp 10.1.2.2:443: connection refused
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.pushImage(DockerConnection.java:1047)
> at org.jboss.tools.openshift.internal.ui.dockerutils.PushImageToRegistryJob.doRun(PushImageToRegistryJob.java:67)
> at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:37)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: com.spotify.docker.client.DockerException: org.eclipse.linuxtools.docker.core.DockerImagePushFailedException: Image push failed: hub.openshift.rhel-cdk.10.1.2.2.xip.io/sample-project/aloha: unable to ping registry endpoint https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v0/
> v2 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v2/: dial tcp 10.1.2.2:443: connection refused
> v1 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v1/_ping: dial tcp 10.1.2.2:443: connection refused
> at org.eclipse.linuxtools.internal.docker.core.DockerProgressHandler.progress(DockerProgressHandler.java:42)
> at com.spotify.docker.client.ProgressStream.tail(ProgressStream.java:74)
> at com.spotify.docker.client.DefaultDockerClient.push(DefaultDockerClient.java:821)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.pushImage(DockerConnection.java:1043)
> ... 3 more
> Caused by: org.eclipse.linuxtools.docker.core.DockerImagePushFailedException: Image push failed: hub.openshift.rhel-cdk.10.1.2.2.xip.io/sample-project/aloha: unable to ping registry endpoint https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v0/
> v2 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v2/: dial tcp 10.1.2.2:443: connection refused
> v1 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v1/_ping: dial tcp 10.1.2.2:443: connection refused
> at org.eclipse.linuxtools.internal.docker.ui.views.ImagePushProgressHandler.processMessage(ImagePushProgressHandler.java:49)
> at org.eclipse.linuxtools.internal.docker.core.DockerProgressHandler.progress(DockerProgressHandler.java:40)
> ... 6 more
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22712) NullPointerException in GettingStartedHtmlPage.updateEarlyAccess
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22712?page=com.atlassian.jira.plugi... ]
Fred Bricon resolved JBIDE-22712.
---------------------------------
Resolution: Done
It seems this error can occur after Central has been closed. Added some null checks to prevent it from happening.
> NullPointerException in GettingStartedHtmlPage.updateEarlyAccess
> ----------------------------------------------------------------
>
> Key: JBIDE-22712
> URL: https://issues.jboss.org/browse/JBIDE-22712
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.3.0.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Fred Bricon
> Fix For: 4.4.1.AM2
>
>
> The following problem was reported via the automated error reporting:
> Message: HIDDEN
> {noformat}
> java.lang.NullPointerException: null
> at org.jboss.tools.central.editors.GettingStartedHtmlPage.updateEarlyAccess(GettingStartedHtmlPage.java:367)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage.access$14(GettingStartedHtmlPage.java:350)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage$6$1.run(GettingStartedHtmlPage.java:335)
> at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:162)
> at org.eclipse.ui.internal.UISynchronizer$3.run(UISynchronizer.java:154)
> 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:4155)
> {noformat}
> Bundles:
> | org.eclipse.swt | 3.104.0.v20150528-0211 | 3.105.0.v20160603-0902 |
> | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.108.0.v20160518-1929 |
> | org.jboss.tools.central | 2.0.0.Final-v20151001-1531-B45 | 2.1.1.Alpha1-v20160623-1622-B929 |
> Operating Systems:
> | Linux | 2.6.32.22 | 4.4.11.fc22 |
> | MacOSX | 10.10.5 | 10.11.5 |
> | Windows | 6.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/5715ca22e4b055563f...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22686) Can't push image to docker registry
by Hardy Ferentschik (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22686?page=com.atlassian.jira.plugi... ]
Hardy Ferentschik commented on JBIDE-22686:
-------------------------------------------
{quote}
So now i think the problem is because 10.1.2.2 is unreachable. Am i right?
{quote}
Right, in fact looking at your _ip addr list_ output, the 10.1.2.2 interface is not even configured. It is usually the _eth1_ interface. _vagrant ssh_ works, since Vagrant uses _eth0_ for this purposes. So your CDK instance was never really properly up and running. I would think nothing OpenShift related would have worked. Hard to tell what the reason was for that. I would expect some form of error somewhere. Was there nothing in the Vagrant logs?
It could be that you had some rouge VirtualBox config. I have seen this sometimes. Basically some VirtualBox state/interface does not get cleaned up and prevents later startups to fail as well.
Now that you have re-installed it is probably hard to dig any further.
> Can't push image to docker registry
> -----------------------------------
>
> Key: JBIDE-22686
> URL: https://issues.jboss.org/browse/JBIDE-22686
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: docker, openshift
> Affects Versions: 4.4.0.Final
> Environment: Fedora 23
> Reporter: Dmitry Bocharov
> Assignee: Dmitry Bocharov
> Fix For: 4.4.x
>
> Attachments: DeployDockerImageToOS.webm, DeployedSuccessfully.webm
>
>
> The screencast of the last steps is attached.
> Properties and settings of the cdk haven't been changed. Everything is dowloaded and installed in a usual way.
> Possibly something is with the dns - maybe it wasn't configured correctly while cdk installation. Because we to push to the valid url, while OS connection only an IP in its settings.
> _exception:_
> org.eclipse.linuxtools.docker.core.DockerException: com.spotify.docker.client.DockerException: org.eclipse.linuxtools.docker.core.DockerImagePushFailedException: Image push failed: hub.openshift.rhel-cdk.10.1.2.2.xip.io/sample-project/aloha: unable to ping registry endpoint https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v0/
> v2 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v2/: dial tcp 10.1.2.2:443: connection refused
> v1 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v1/_ping: dial tcp 10.1.2.2:443: connection refused
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.pushImage(DockerConnection.java:1047)
> at org.jboss.tools.openshift.internal.ui.dockerutils.PushImageToRegistryJob.doRun(PushImageToRegistryJob.java:67)
> at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:37)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: com.spotify.docker.client.DockerException: org.eclipse.linuxtools.docker.core.DockerImagePushFailedException: Image push failed: hub.openshift.rhel-cdk.10.1.2.2.xip.io/sample-project/aloha: unable to ping registry endpoint https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v0/
> v2 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v2/: dial tcp 10.1.2.2:443: connection refused
> v1 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v1/_ping: dial tcp 10.1.2.2:443: connection refused
> at org.eclipse.linuxtools.internal.docker.core.DockerProgressHandler.progress(DockerProgressHandler.java:42)
> at com.spotify.docker.client.ProgressStream.tail(ProgressStream.java:74)
> at com.spotify.docker.client.DefaultDockerClient.push(DefaultDockerClient.java:821)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.pushImage(DockerConnection.java:1043)
> ... 3 more
> Caused by: org.eclipse.linuxtools.docker.core.DockerImagePushFailedException: Image push failed: hub.openshift.rhel-cdk.10.1.2.2.xip.io/sample-project/aloha: unable to ping registry endpoint https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v0/
> v2 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v2/: dial tcp 10.1.2.2:443: connection refused
> v1 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v1/_ping: dial tcp 10.1.2.2:443: connection refused
> at org.eclipse.linuxtools.internal.docker.ui.views.ImagePushProgressHandler.processMessage(ImagePushProgressHandler.java:49)
> at org.eclipse.linuxtools.internal.docker.core.DockerProgressHandler.progress(DockerProgressHandler.java:40)
> ... 6 more
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22712) NullPointerException in GettingStartedHtmlPage.updateEarlyAccess
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22712?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-22712:
-----------------------------------
Assignee: Fred Bricon
> NullPointerException in GettingStartedHtmlPage.updateEarlyAccess
> ----------------------------------------------------------------
>
> Key: JBIDE-22712
> URL: https://issues.jboss.org/browse/JBIDE-22712
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.3.0.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Fred Bricon
> Fix For: 4.4.1.AM2
>
>
> The following problem was reported via the automated error reporting:
> Message: HIDDEN
> {noformat}
> java.lang.NullPointerException: null
> at org.jboss.tools.central.editors.GettingStartedHtmlPage.updateEarlyAccess(GettingStartedHtmlPage.java:367)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage.access$14(GettingStartedHtmlPage.java:350)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage$6$1.run(GettingStartedHtmlPage.java:335)
> at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:162)
> at org.eclipse.ui.internal.UISynchronizer$3.run(UISynchronizer.java:154)
> 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:4155)
> {noformat}
> Bundles:
> | org.eclipse.swt | 3.104.0.v20150528-0211 | 3.105.0.v20160603-0902 |
> | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.108.0.v20160518-1929 |
> | org.jboss.tools.central | 2.0.0.Final-v20151001-1531-B45 | 2.1.1.Alpha1-v20160623-1622-B929 |
> Operating Systems:
> | Linux | 2.6.32.22 | 4.4.11.fc22 |
> | MacOSX | 10.10.5 | 10.11.5 |
> | Windows | 6.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/5715ca22e4b055563f...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22712) NullPointerException in GettingStartedHtmlPage.updateEarlyAccess
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22712?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-22712:
--------------------------------
Fix Version/s: 4.4.1.AM2
Story Points: 1
Sprint: devex #117 July 2016
> NullPointerException in GettingStartedHtmlPage.updateEarlyAccess
> ----------------------------------------------------------------
>
> Key: JBIDE-22712
> URL: https://issues.jboss.org/browse/JBIDE-22712
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.3.0.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Fred Bricon
> Fix For: 4.4.1.AM2
>
>
> The following problem was reported via the automated error reporting:
> Message: HIDDEN
> {noformat}
> java.lang.NullPointerException: null
> at org.jboss.tools.central.editors.GettingStartedHtmlPage.updateEarlyAccess(GettingStartedHtmlPage.java:367)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage.access$14(GettingStartedHtmlPage.java:350)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage$6$1.run(GettingStartedHtmlPage.java:335)
> at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:162)
> at org.eclipse.ui.internal.UISynchronizer$3.run(UISynchronizer.java:154)
> 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:4155)
> {noformat}
> Bundles:
> | org.eclipse.swt | 3.104.0.v20150528-0211 | 3.105.0.v20160603-0902 |
> | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.108.0.v20160518-1929 |
> | org.jboss.tools.central | 2.0.0.Final-v20151001-1531-B45 | 2.1.1.Alpha1-v20160623-1622-B929 |
> Operating Systems:
> | Linux | 2.6.32.22 | 4.4.11.fc22 |
> | MacOSX | 10.10.5 | 10.11.5 |
> | Windows | 6.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/5715ca22e4b055563f...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22712) NullPointerException in GettingStartedHtmlPage.updateEarlyAccess
by Automated Error Reporting Bot (JIRA)
Automated Error Reporting Bot created JBIDE-22712:
-----------------------------------------------------
Summary: NullPointerException in GettingStartedHtmlPage.updateEarlyAccess
Key: JBIDE-22712
URL: https://issues.jboss.org/browse/JBIDE-22712
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: central
Affects Versions: 4.3.0.Final
Reporter: Automated Error Reporting Bot
The following problem was reported via the automated error reporting:
Message: HIDDEN
{noformat}
java.lang.NullPointerException: null
at org.jboss.tools.central.editors.GettingStartedHtmlPage.updateEarlyAccess(GettingStartedHtmlPage.java:367)
at org.jboss.tools.central.editors.GettingStartedHtmlPage.access$14(GettingStartedHtmlPage.java:350)
at org.jboss.tools.central.editors.GettingStartedHtmlPage$6$1.run(GettingStartedHtmlPage.java:335)
at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:162)
at org.eclipse.ui.internal.UISynchronizer$3.run(UISynchronizer.java:154)
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:4155)
{noformat}
Bundles:
| org.eclipse.swt | 3.104.0.v20150528-0211 | 3.105.0.v20160603-0902 |
| org.eclipse.ui | 3.107.0.v20150507-1945 | 3.108.0.v20160518-1929 |
| org.jboss.tools.central | 2.0.0.Final-v20151001-1531-B45 | 2.1.1.Alpha1-v20160623-1622-B929 |
Operating Systems:
| Linux | 2.6.32.22 | 4.4.11.fc22 |
| MacOSX | 10.10.5 | 10.11.5 |
| Windows | 6.1.0 | 10.0.0 |
The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/5715ca22e4b055563f...] for the latest data.
Thank you for your assistance.
Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months