[JBoss JIRA] (JBIDE-22710) NullPointerException in JBossCentralActivator.openJBossCentralEditor
by Automated Error Reporting Bot (JIRA)
Automated Error Reporting Bot created JBIDE-22710:
-----------------------------------------------------
Summary: NullPointerException in JBossCentralActivator.openJBossCentralEditor
Key: JBIDE-22710
URL: https://issues.jboss.org/browse/JBIDE-22710
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: central
Affects Versions: 4.3.1.Final
Reporter: Automated Error Reporting Bot
The following problem was reported via the automated error reporting:
Message: Unhandled event loop exception
{noformat}
java.lang.NullPointerException: null
at org.jboss.tools.central.JBossCentralActivator.openJBossCentralEditor(JBossCentralActivator.java:435)
at org.jboss.tools.central.JBossCentralActivator.getJBossCentralEditor(JBossCentralActivator.java:386)
at org.jboss.tools.central.actions.ShowJBossCentralHandler.execute(ShowJBossCentralHandler.java:29)
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.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-2)
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.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
{noformat}
Bundles:
| org.eclipse.e4.core.di | 1.5.0.v20150421-2214 | 1.6.0.v20160319-0612 |
| org.eclipse.ui | 3.107.0.v20150507-1945 | 3.108.0.v20160518-1929 |
| org.jboss.tools.central | 2.0.1.Final-v20160401-1059-B103 | 2.1.0.Final-v20160613-2000-B8 |
Operating Systems:
| Linux | 3.13.0 | 4.4.9.fc23 |
| Windows | 10.0.0 | 10.0.0 |
The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/571e5eaee4b08bd809...] 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 Dmitry Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22686?page=com.atlassian.jira.plugi... ]
Dmitry Bocharov commented on JBIDE-22686:
-----------------------------------------
[~hardy.ferentschik],
{code:shell}
[vagrant@rhel-cdk ~]$ ip addr list
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 52:54:00:ab:b6:9e brd ff:ff:ff:ff:ff:ff
inet 192.168.121.51/24 brd 192.168.121.255 scope global dynamic eth0
valid_lft 2384sec preferred_lft 2384sec
inet6 fe80::5054:ff:feab:b69e/64 scope link
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 52:54:00:09:6a:57 brd ff:ff:ff:ff:ff:ff
4: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
link/ether 02:42:5b:82:ad:f4 brd ff:ff:ff:ff:ff:ff
inet 172.17.0.1/16 scope global docker0
valid_lft forever preferred_lft forever
inet6 fe80::42:5bff:fe82:adf4/64 scope link
valid_lft forever preferred_lft forever
10: veth046d304@if9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP
link/ether 2a:b6:bf:85:4a:d4 brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet6 fe80::28b6:bfff:fe85:4ad4/64 scope link
valid_lft forever preferred_lft forever
{code}
{code:shell}
[vagrant@rhel-cdk ~]$ ping 10.1.2.2
PING 10.1.2.2 (10.1.2.2) 56(84) bytes of data.
>From 192.168.121.1 icmp_seq=1 Destination Port Unreachable
>From 192.168.121.1 icmp_seq=2 Destination Port Unreachable
{code}
yes, i tried vagrant destroy and vagrant up several times.
I also tried every step from home (where i have router - thought it could be the reason of the problem) and from the office.
So now i think the problem is because 10.1.2.2 is unreachable. Am i right?
> 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
>
>
> 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-22709) Application Wizard: Prompt to create a new project if there is none is not shown
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-22709:
-------------------------------------
Summary: Application Wizard: Prompt to create a new project if there is none is not shown
Key: JBIDE-22709
URL: https://issues.jboss.org/browse/JBIDE-22709
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.4.1.AM2
Reporter: Marián Labuda
When I have an OpenShift 3 connection without any projects on it, there was a prompt to create a new project (New Project dialog has been opened upon opening of New OpenShift Application wizard). Now when I open a New OpenShift Application Wizard on a connection without any project there is no prompt to create it.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22708) NullPointerException in AbstractKiePropertyPage.getResourceHandler
by Automated Error Reporting Bot (JIRA)
Automated Error Reporting Bot created JBIDE-22708:
-----------------------------------------------------
Summary: NullPointerException in AbstractKiePropertyPage.getResourceHandler
Key: JBIDE-22708
URL: https://issues.jboss.org/browse/JBIDE-22708
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jbpm
Reporter: Automated Error Reporting Bot
Assignee: Koen Aers
The following problem was reported via the automated error reporting:
Message: HIDDEN
{noformat}
java.lang.NullPointerException: null
at org.kie.eclipse.navigator.preferences.AbstractKiePropertyPage.getResourceHandler(AbstractKiePropertyPage.java:85)
at org.kie.eclipse.navigator.preferences.ServerPropertyPage.createFieldEditors(ServerPropertyPage.java:31)
at org.kie.eclipse.navigator.preferences.FieldEditorPropertyPage.createContents(FieldEditorPropertyPage.java:183)
at org.kie.eclipse.navigator.preferences.AbstractKiePropertyPage.createContents(AbstractKiePropertyPage.java:47)
at org.eclipse.jface.preference.PreferencePage.createControl(PreferencePage.java:241)
at org.eclipse.jface.preference.PreferenceDialog.createPageControl(PreferenceDialog.java:1450)
at org.eclipse.jface.preference.PreferenceDialog$13.run(PreferenceDialog.java:1217)
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.preference.PreferenceDialog.showPage(PreferenceDialog.java:1209)
at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.showPage(FilteredPreferenceDialog.java:608)
at org.eclipse.jface.preference.PreferenceDialog$9$1.run(PreferenceDialog.java:675)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.jface.preference.PreferenceDialog$9.selectionChanged(PreferenceDialog.java:670)
at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:877)
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:874)
at org.eclipse.jface.viewers.StructuredViewer.handlePostSelect(StructuredViewer.java:1243)
at org.eclipse.jface.viewers.StructuredViewer$5.widgetSelected(StructuredViewer.java:1269)
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$2.run(OpenStrategy.java:440)
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:3794)
{noformat}
Bundles:
| org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.11.1.v20150903-1804 |
| org.eclipse.jface | 3.11.1.v20160128-1644 | 3.11.1.v20160128-1644 |
| org.eclipse.swt | 3.104.2.v20160212-1350 | 3.104.2.v20160212-1350 |
| org.eclipse.ui | 3.107.0.v20150507-1945 | 3.107.0.v20150507-1945 |
| org.kie.eclipse.navigator | 6.4.0.201601201107 | 6.4.1.Final-v20160503-1355-B205 |
Operating Systems:
| Linux | 2.6.32.1 | 4.4.0 |
| MacOSX | 10.11.5 | 10.11.5 |
| Windows | 6.2.0 | 10.0.0 |
The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/571952bee4b0cd449c...] 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 edited comment on JBIDE-22686 at 7/11/16 4:45 AM:
--------------------------------------------------------------------
{quote}yes, of course, it is up. Vagrant ssh enters the VM.{quote}
Ok. What's the output of _ip addr list_?
{quote}
Hardy, what do you mean by different IP? I haven't changed any IP options myself
{quote}
I was just wondering whether you are using a non default IP, especially due to the "no route to host". Can you access the OpenShift console and build applications? Can you ping 10.1.2.2?
Have you tried re-creating the VM (_vagrant destroy -f && vagrant up_)?
was (Author: hardy.ferentschik):
{quote}yes, of course, it is up. Vagrant ssh enters the VM.{quote}
Ok. What's the output of {code}ip addr list{code}?
{quote}
Hardy, what do you mean by different IP? I haven't changed any IP options myself
{quote}
I was just wondering whether you are using a non default IP, especially due to the "no route to host". Can you access the OpenShift console and build applications? Can you ping 10.1.2.2?
Have you tried re-creating the VM ({code}vagrant destroy -f && vagrant up{code})?
> 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
>
>
> 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-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}yes, of course, it is up. Vagrant ssh enters the VM.{quote}
Ok. What's the output of {code}ip addr list{code}?
{quote}
Hardy, what do you mean by different IP? I haven't changed any IP options myself
{quote}
I was just wondering whether you are using a non default IP, especially due to the "no route to host". Can you access the OpenShift console and build applications? Can you ping 10.1.2.2?
Have you tried re-creating the VM ({code}vagrant destroy -f && vagrant up{code})?
> 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
>
>
> 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-21828) OpenShift Explorer view flickers when refreshing a service
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21828?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21828.
---------------------------------
Verified in devstudio AM1-v20160711-0432-B5652.
> OpenShift Explorer view flickers when refreshing a service
> ----------------------------------------------------------
>
> Key: JBIDE-21828
> URL: https://issues.jboss.org/browse/JBIDE-21828
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Assignee: Thomas Mäder
> Fix For: 4.4.1.AM1
>
> Attachments: Screenshot 2016-03-08 10.32.39.png
>
>
> When calling the "Refresh" command on a service, the tree view flickers because of too many refresh calls.
> Adding some traces revealed 25 calls to {{BaseExplorerContentProvider#refreshViewer(Object)}}, which seems way too much for a service with a single pod.
> Attachement: screenshot of the OpenShift Server view, showing 2 projects, one of which has 3 services.
> Custom/added logs in the console:
> {code}
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/mongodb
> Refreshing viewer from sample/mongodb
> Refreshing viewer from sample/mongodb
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22677) rsync stuck on OSX
by Dmitry Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22677?page=com.atlassian.jira.plugi... ]
Dmitry Bocharov reassigned JBIDE-22677:
---------------------------------------
Assignee: Fred Bricon (was: Dmitry Bocharov)
> rsync stuck on OSX
> ------------------
>
> Key: JBIDE-22677
> URL: https://issues.jboss.org/browse/JBIDE-22677
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 4.4.x
>
>
> I deployed an eap app from the eap64-basic-s2i template, then created an openshift 3 server.
> On server startup, publishing fails to complete after 5 minutes and a thread dump shows rsync is still blocking in the background.
> {noformat}
> "pool-40-thread-1" #231 prio=5 os_prio=31 tid=0x00007f9a55dd0000 nid=0xeb9f runnable [0x000000013199a000]
> java.lang.Thread.State: RUNNABLE
> at java.io.FileInputStream.readBytes(Native Method)
> at java.io.FileInputStream.read(FileInputStream.java:255)
> at java.io.BufferedInputStream.read1(BufferedInputStream.java:284)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:345)
> - locked <0x00000007b3d45cb8> (a java.lang.UNIXProcess$ProcessPipeInputStream)
> at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
> at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326)
> at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)
> - locked <0x00000007b3d49d50> (a java.io.InputStreamReader)
> at java.io.InputStreamReader.read(InputStreamReader.java:184)
> at java.io.BufferedReader.fill(BufferedReader.java:161)
> at java.io.BufferedReader.readLine(BufferedReader.java:324)
> - locked <0x00000007b3d49d50> (a java.io.InputStreamReader)
> at java.io.BufferedReader.readLine(BufferedReader.java:389)
> at org.jboss.tools.openshift.core.server.RSync.lambda$0(RSync.java:152)
> at org.jboss.tools.openshift.core.server.RSync$$Lambda$181/1635081930.run(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> I'm deploying on CDK 2.1RC5
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months