[JBoss JIRA] (JBIDE-21986) Error when opening the "Deploy Docker Image" wizard if no valid Docker connection exists
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21986?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21986:
-------------------------------------
Fix Version/s: 4.3.1.CR1
> Error when opening the "Deploy Docker Image" wizard if no valid Docker connection exists
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-21986
> URL: https://issues.jboss.org/browse/JBIDE-21986
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Xavier Coulon
> Fix For: 4.3.1.CR1
>
>
> When opening the {{Deploy Docker Image}} wizard, I got an error as below:
> {code}
> !ENTRY org.eclipse.core.databinding.observable 4 2 2016-03-29 10:52:05.197
> !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.databinding.observable".
> !STACK 0
> java.lang.RuntimeException: java.lang.NullPointerException
> at org.eclipse.core.internal.databinding.beans.BeanPropertyHelper.readProperty(BeanPropertyHelper.java:102)
> at org.eclipse.core.internal.databinding.beans.BeanValueProperty.doGetValue(BeanValueProperty.java:49)
> at org.eclipse.core.databinding.property.value.ValueProperty.getValue(ValueProperty.java:58)
> at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue$2.run(SimplePropertyObservableValue.java:84)
> at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:150)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:154)
> at org.eclipse.core.databinding.observable.Realm.exec(Realm.java:172)
> at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.firstListenerAdded(SimplePropertyObservableValue.java:81)
> at org.eclipse.core.databinding.observable.ChangeManager.addListener(ChangeManager.java:70)
> at org.eclipse.core.databinding.observable.value.AbstractObservableValue.addValueChangeListener(AbstractObservableValue.java:47)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.firstListenerAdded(DecoratingObservableValue.java:76)
> at org.eclipse.core.databinding.observable.ChangeManager.addListener(ChangeManager.java:70)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.addValueChangeListener(DecoratingObservableValue.java:45)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.firstListenerAdded(DecoratingObservableValue.java:76)
> at org.eclipse.core.databinding.observable.ChangeManager.addListener(ChangeManager.java:70)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.addValueChangeListener(DecoratingObservableValue.java:45)
> at org.eclipse.core.databinding.ValueBinding.<init>(ValueBinding.java:81)
> at org.eclipse.core.databinding.DataBindingContext.bindValue(DataBindingContext.java:164)
> at org.jboss.tools.common.ui.databinding.ValueBindingBuilder.bind(ValueBindingBuilder.java:36)
> at org.jboss.tools.common.ui.databinding.ValueBindingBuilder.access$0(ValueBindingBuilder.java:34)
> at org.jboss.tools.common.ui.databinding.ValueBindingBuilder$ModelDefinition.in(ValueBindingBuilder.java:69)
> at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImagePage.createDockerConnectionControl(DeployImagePage.java:226)
> at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImagePage.doCreateControls(DeployImagePage.java:158)
> at org.jboss.tools.openshift.internal.common.ui.wizard.AbstractOpenShiftWizardPage.createControl(AbstractOpenShiftWizardPage.java:70)
> at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:175)
> at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:705)
> at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:597)
> at org.eclipse.jface.window.Window.create(Window.java:430)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1096)
> at org.jboss.tools.common.ui.WizardUtils.createWizardDialog(WizardUtils.java:262)
> at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:255)
> at org.jboss.tools.openshift.internal.ui.handler.DeployImageHandler.execute(DeployImageHandler.java:58)
> 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(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.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234)
> 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:493)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:799)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:675)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:659)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:592)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4230)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1491)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1514)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1499)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1299)
> 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: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)
> Caused by: java.lang.NullPointerException
> at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImageWizardModel.setDockerConnection(DeployImageWizardModel.java:465)
> at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImageWizardModel.getDockerConnection(DeployImageWizardModel.java:116)
> 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.core.internal.databinding.beans.BeanPropertyHelper.readProperty(BeanPropertyHelper.java:96)
> ... 80 more
> {code}
> I had a single Docker connection, but it was not reachable:
> {code}
> Caused by: java.net.SocketTimeoutException: connect timed out
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345)
> at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
> at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> at java.net.Socket.connect(Socket.java:589)
> at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:244)
> at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:125)
> ... 29 more
> {code}
> so the list of images could not be retrieved.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21986) Error when opening the "Deploy Docker Image" wizard if no valid Docker connection exists
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21986?page=com.atlassian.jira.plugi... ]
Xavier Coulon reassigned JBIDE-21986:
-------------------------------------
Assignee: Xavier Coulon
> Error when opening the "Deploy Docker Image" wizard if no valid Docker connection exists
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-21986
> URL: https://issues.jboss.org/browse/JBIDE-21986
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.3.1.CR1
>
>
> When opening the {{Deploy Docker Image}} wizard, I got an error as below:
> {code}
> !ENTRY org.eclipse.core.databinding.observable 4 2 2016-03-29 10:52:05.197
> !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.databinding.observable".
> !STACK 0
> java.lang.RuntimeException: java.lang.NullPointerException
> at org.eclipse.core.internal.databinding.beans.BeanPropertyHelper.readProperty(BeanPropertyHelper.java:102)
> at org.eclipse.core.internal.databinding.beans.BeanValueProperty.doGetValue(BeanValueProperty.java:49)
> at org.eclipse.core.databinding.property.value.ValueProperty.getValue(ValueProperty.java:58)
> at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue$2.run(SimplePropertyObservableValue.java:84)
> at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:150)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:154)
> at org.eclipse.core.databinding.observable.Realm.exec(Realm.java:172)
> at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.firstListenerAdded(SimplePropertyObservableValue.java:81)
> at org.eclipse.core.databinding.observable.ChangeManager.addListener(ChangeManager.java:70)
> at org.eclipse.core.databinding.observable.value.AbstractObservableValue.addValueChangeListener(AbstractObservableValue.java:47)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.firstListenerAdded(DecoratingObservableValue.java:76)
> at org.eclipse.core.databinding.observable.ChangeManager.addListener(ChangeManager.java:70)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.addValueChangeListener(DecoratingObservableValue.java:45)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.firstListenerAdded(DecoratingObservableValue.java:76)
> at org.eclipse.core.databinding.observable.ChangeManager.addListener(ChangeManager.java:70)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.addValueChangeListener(DecoratingObservableValue.java:45)
> at org.eclipse.core.databinding.ValueBinding.<init>(ValueBinding.java:81)
> at org.eclipse.core.databinding.DataBindingContext.bindValue(DataBindingContext.java:164)
> at org.jboss.tools.common.ui.databinding.ValueBindingBuilder.bind(ValueBindingBuilder.java:36)
> at org.jboss.tools.common.ui.databinding.ValueBindingBuilder.access$0(ValueBindingBuilder.java:34)
> at org.jboss.tools.common.ui.databinding.ValueBindingBuilder$ModelDefinition.in(ValueBindingBuilder.java:69)
> at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImagePage.createDockerConnectionControl(DeployImagePage.java:226)
> at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImagePage.doCreateControls(DeployImagePage.java:158)
> at org.jboss.tools.openshift.internal.common.ui.wizard.AbstractOpenShiftWizardPage.createControl(AbstractOpenShiftWizardPage.java:70)
> at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:175)
> at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:705)
> at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:597)
> at org.eclipse.jface.window.Window.create(Window.java:430)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1096)
> at org.jboss.tools.common.ui.WizardUtils.createWizardDialog(WizardUtils.java:262)
> at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:255)
> at org.jboss.tools.openshift.internal.ui.handler.DeployImageHandler.execute(DeployImageHandler.java:58)
> 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(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.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234)
> 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:493)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:799)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:675)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:659)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:592)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4230)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1491)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1514)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1499)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1299)
> 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: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)
> Caused by: java.lang.NullPointerException
> at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImageWizardModel.setDockerConnection(DeployImageWizardModel.java:465)
> at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImageWizardModel.getDockerConnection(DeployImageWizardModel.java:116)
> 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.core.internal.databinding.beans.BeanPropertyHelper.readProperty(BeanPropertyHelper.java:96)
> ... 80 more
> {code}
> I had a single Docker connection, but it was not reachable:
> {code}
> Caused by: java.net.SocketTimeoutException: connect timed out
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345)
> at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
> at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> at java.net.Socket.connect(Socket.java:589)
> at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:244)
> at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:125)
> ... 29 more
> {code}
> so the list of images could not be retrieved.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21983) RuntimeException when trying to see Docker containers/images
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21983?page=com.atlassian.jira.plugi... ]
Xavier Coulon commented on JBIDE-21983:
---------------------------------------
[~akazakov] I could not reproduce the issue but after looking for some information, I found this:
http://stackoverflow.com/questions/25740556/error-while-using-jersey-clie...
In the OSGi console, I could verify that all the bundles referenced in the SO response were actually {{RESOLVED}} or {{STARTED}} in my case:
{code}
osgi> ss | grep hk
1074 ACTIVE org.glassfish.hk2.api_2.3.0.b10_v201508191500
1075 ACTIVE org.glassfish.hk2.locator_2.3.0.b10_v201508191500
1076 ACTIVE org.glassfish.hk2.osgi-resource-locator_2.3.0.b10_v201508191500
1077 ACTIVE org.glassfish.hk2.utils_2.3.0.b10_v201508191500
true
{code}
{code}
osgi> ss | grep javax.inject
41 RESOLVED javax.inject_1.0.0.v20091030
true
{code}
{code}
osgi> ss | grep guava
16 RESOLVED com.fasterxml.jackson.datatype.jackson-datatype-guava_2.5.0.v201504151636
20 RESOLVED com.google.guava_15.0.0.v201403281430
21 RESOLVED com.google.guava_13.0.0
1079 RESOLVED org.glassfish.jersey.bundles.repackaged.jersey-guava_2.14.0.v201504151636
true
{code}
Could you please let me know if your runtime has these bundles, too ?
Also, this has been reported in JBDS-3688, too
> RuntimeException when trying to see Docker containers/images
> ------------------------------------------------------------
>
> Key: JBIDE-21983
> URL: https://issues.jboss.org/browse/JBIDE-21983
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: docker
> Affects Versions: 4.3.1.CR1
> Reporter: Alexey Kazakov
> Assignee: Xavier Coulon
> Priority: Critical
>
> 1. CDK sever adapter -> Show In -> Docker Explorer
> 2. Unfold Containers or Images of the rhel-ose CDK Server:
> {code}
> java.lang.RuntimeException: java.lang.ClassNotFoundException: Provider org.glassfish.jersey.internal.RuntimeDelegateImpl could not be instantiated: java.lang.IllegalStateException: No generator was provided and there is no default generator registered
> at javax.ws.rs.ext.RuntimeDelegate.findDelegate(RuntimeDelegate.java:152)
> at javax.ws.rs.ext.RuntimeDelegate.getInstance(RuntimeDelegate.java:120)
> at javax.ws.rs.core.UriBuilder.newInstance(UriBuilder.java:95)
> at javax.ws.rs.core.UriBuilder.fromUri(UriBuilder.java:106)
> at org.glassfish.jersey.client.JerseyWebTarget.<init>(JerseyWebTarget.java:82)
> at org.glassfish.jersey.client.JerseyClient.target(JerseyClient.java:192)
> at org.glassfish.jersey.client.JerseyClient.target(JerseyClient.java:70)
> at com.spotify.docker.client.DefaultDockerClient.resource(DefaultDockerClient.java:1051)
> at com.spotify.docker.client.DefaultDockerClient.listImages(DefaultDockerClient.java:320)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.listImages(DockerConnection.java:787)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getImages(DockerConnection.java:750)
> at org.eclipse.linuxtools.internal.docker.ui.views.DockerExplorerContentProvider$5.run(DockerExplorerContentProvider.java:241)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.lang.ClassNotFoundException: Provider org.glassfish.jersey.internal.RuntimeDelegateImpl could not be instantiated: java.lang.IllegalStateException: No generator was provided and there is no default generator registered
> at javax.ws.rs.ext.FactoryFinder.newInstance(FactoryFinder.java:122)
> at javax.ws.rs.ext.FactoryFinder.find(FactoryFinder.java:225)
> at javax.ws.rs.ext.RuntimeDelegate.findDelegate(RuntimeDelegate.java:135)
> ... 12 more
> Caused by: java.lang.IllegalStateException: No generator was provided and there is no default generator registered
> at org.glassfish.hk2.internal.ServiceLocatorFactoryImpl.internalCreate(ServiceLocatorFactoryImpl.java:266)
> at org.glassfish.hk2.internal.ServiceLocatorFactoryImpl.create(ServiceLocatorFactoryImpl.java:247)
> at org.glassfish.jersey.internal.inject.Injections._createLocator(Injections.java:138)
> at org.glassfish.jersey.internal.inject.Injections.createLocator(Injections.java:109)
> at org.glassfish.jersey.internal.RuntimeDelegateImpl.<init>(RuntimeDelegateImpl.java:61)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at java.lang.Class.newInstance(Class.java:442)
> at javax.ws.rs.ext.FactoryFinder.newInstance(FactoryFinder.java:118)
> ... 14 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21972) Improve initialization of Configure Service Ports dialog
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21972?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21972:
-------------------------------------
Labels: deploy_docker_wizard openshift_v3 (was: )
> Improve initialization of Configure Service Ports dialog
> --------------------------------------------------------
>
> Key: JBIDE-21972
> URL: https://issues.jboss.org/browse/JBIDE-21972
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.3.1.CR1
>
>
> When "Add..." is run on page 'Services & Routing Settings, if list of service ports is not empty, dialog is pre-filled with integers. Some errors should be fixed:
> Case #1
> # ASSERT: have a project in OpenShift
> # EXEC: in Explorer: choose "Deploy Docker Image..." in context menu of your project
> # EXEC: in deploy docker image wizard: pick an image (ex. php),
> # EXEC: confirm the 2nd wizard page ("Deployment Configuration & Scalability") and get to the 3rd wizard page
> # ASSERT: no ports are defined yet
> # EXEC: Create service port=65535, pod port=2000
> # EXEC: Run "Add..." second time.
> Result:
> Service port is filled with 65535 and causes error message.
> Pod port is filled with 65536 also causing error.
> Case #2
> # ASSERT: no ports are defined yet.
> # EXEC: Create service port=2000, pod port=2001
> # EXEC: Run "Add..." second time.
> Result:
> Service port is filled with 2001 - it is ok.
> Pod port is filled with 2001 causing error.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21987) Improve initialization of Configure Service Ports dialog
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-21987:
----------------------------------------
Summary: Improve initialization of Configure Service Ports dialog
Key: JBIDE-21987
URL: https://issues.jboss.org/browse/JBIDE-21987
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.CR1
Reporter: Viacheslav Kabanovich
Assignee: Viacheslav Kabanovich
Fix For: 4.3.1.CR1
When "Add..." is run on page 'Services & Routing Settings, if list of service ports is not empty, dialog is pre-filled with integers. Some errors should be fixed:
Case #1
# ASSERT: have a project in OpenShift
# EXEC: in Explorer: choose "Deploy Docker Image..." in context menu of your project
# EXEC: in deploy docker image wizard: pick an image (ex. php),
# EXEC: confirm the 2nd wizard page ("Deployment Configuration & Scalability") and get to the 3rd wizard page
# ASSERT: no ports are defined yet
# EXEC: Create service port=65535, pod port=2000
# EXEC: Run "Add..." second time.
Result:
Service port is filled with 65535 and causes error message.
Pod port is filled with 65536 also causing error.
Case #2
# ASSERT: no ports are defined yet.
# EXEC: Create service port=2000, pod port=2001
# EXEC: Run "Add..." second time.
Result:
Service port is filled with 2001 - it is ok.
Pod port is filled with 2001 causing error.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21987) Improve initialization of Configure Service Ports dialog
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21987?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21987:
-------------------------------------
Fix Version/s: 4.4.0.Alpha1
(was: 4.3.1.CR1)
> Improve initialization of Configure Service Ports dialog
> --------------------------------------------------------
>
> Key: JBIDE-21987
> URL: https://issues.jboss.org/browse/JBIDE-21987
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.0.Alpha1
>
>
> When "Add..." is run on page 'Services & Routing Settings, if list of service ports is not empty, dialog is pre-filled with integers. Some errors should be fixed:
> Case #1
> # ASSERT: have a project in OpenShift
> # EXEC: in Explorer: choose "Deploy Docker Image..." in context menu of your project
> # EXEC: in deploy docker image wizard: pick an image (ex. php),
> # EXEC: confirm the 2nd wizard page ("Deployment Configuration & Scalability") and get to the 3rd wizard page
> # ASSERT: no ports are defined yet
> # EXEC: Create service port=65535, pod port=2000
> # EXEC: Run "Add..." second time.
> Result:
> Service port is filled with 65535 and causes error message.
> Pod port is filled with 65536 also causing error.
> Case #2
> # ASSERT: no ports are defined yet.
> # EXEC: Create service port=2000, pod port=2001
> # EXEC: Run "Add..." second time.
> Result:
> Service port is filled with 2001 - it is ok.
> Pod port is filled with 2001 causing error.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21972) Improve initialization of Configure Service Ports dialog
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21972?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21972:
------------------------------------------
[~scabanovich] Thanks!
tested and merged into jbosstools-4.3.x.
> Improve initialization of Configure Service Ports dialog
> --------------------------------------------------------
>
> Key: JBIDE-21972
> URL: https://issues.jboss.org/browse/JBIDE-21972
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Fix For: 4.3.1.CR1
>
>
> When "Add..." is run on page 'Services & Routing Settings, if list of service ports is not empty, dialog is pre-filled with integers. Some errors should be fixed:
> Case #1
> # ASSERT: have a project in OpenShift
> # EXEC: in Explorer: choose "Deploy Docker Image..." in context menu of your project
> # EXEC: in deploy docker image wizard: pick an image (ex. php),
> # EXEC: confirm the 2nd wizard page ("Deployment Configuration & Scalability") and get to the 3rd wizard page
> # ASSERT: no ports are defined yet
> # EXEC: Create service port=65535, pod port=2000
> # EXEC: Run "Add..." second time.
> Result:
> Service port is filled with 65535 and causes error message.
> Pod port is filled with 65536 also causing error.
> Case #2
> # ASSERT: no ports are defined yet.
> # EXEC: Create service port=2000, pod port=2001
> # EXEC: Run "Add..." second time.
> Result:
> Service port is filled with 2001 - it is ok.
> Pod port is filled with 2001 causing error.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21972) Improve initialization of Configure Service Ports dialog
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21972?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21972:
-------------------------------------
Fix Version/s: 4.3.1.CR1
> Improve initialization of Configure Service Ports dialog
> --------------------------------------------------------
>
> Key: JBIDE-21972
> URL: https://issues.jboss.org/browse/JBIDE-21972
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Fix For: 4.3.1.CR1
>
>
> When "Add..." is run on page 'Services & Routing Settings, if list of service ports is not empty, dialog is pre-filled with integers. Some errors should be fixed:
> Case #1
> # ASSERT: have a project in OpenShift
> # EXEC: in Explorer: choose "Deploy Docker Image..." in context menu of your project
> # EXEC: in deploy docker image wizard: pick an image (ex. php),
> # EXEC: confirm the 2nd wizard page ("Deployment Configuration & Scalability") and get to the 3rd wizard page
> # ASSERT: no ports are defined yet
> # EXEC: Create service port=65535, pod port=2000
> # EXEC: Run "Add..." second time.
> Result:
> Service port is filled with 65535 and causes error message.
> Pod port is filled with 65536 also causing error.
> Case #2
> # ASSERT: no ports are defined yet.
> # EXEC: Create service port=2000, pod port=2001
> # EXEC: Run "Add..." second time.
> Result:
> Service port is filled with 2001 - it is ok.
> Pod port is filled with 2001 causing error.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21972) Improve initialization of Configure Service Ports dialog
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21972?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21972:
-------------------------------------
Description:
When "Add..." is run on page 'Services & Routing Settings, if list of service ports is not empty, dialog is pre-filled with integers. Some errors should be fixed:
Case #1
# ASSERT: have a project in OpenShift
# EXEC: in Explorer: choose "Deploy Docker Image..." in context menu of your project
# EXEC: in deploy docker image wizard: pick an image (ex. php),
# EXEC: confirm the 2nd wizard page ("Deployment Configuration & Scalability") and get to the 3rd wizard page
# ASSERT: no ports are defined yet
# EXEC: Create service port=65535, pod port=2000
# EXEC: Run "Add..." second time.
Result:
Service port is filled with 65535 and causes error message.
Pod port is filled with 65536 also causing error.
Case #2
# ASSERT: no ports are defined yet.
# EXEC: Create service port=2000, pod port=2001
# EXEC: Run "Add..." second time.
Result:
Service port is filled with 2001 - it is ok.
Pod port is filled with 2001 causing error.
was:
When "Add..." is run on page 'Services & Routing Settings, if list of service ports is not empty, dialog is pre-filled with integers. Some errors should be fixed:
Start with empty list.
Create service port=65535, pod port=2000
Run "Add..." second time.
Result:
Service port is filled with 65535 and causes error message.
Pod port is filled with 65536 also causing error.
Start with empty list.
Create service port=2000, pod port=2001
Run "Add..." second time.
Result:
Service port is filled with 2001 - it is ok.
Pod port is filled with 2001 causing error.
> Improve initialization of Configure Service Ports dialog
> --------------------------------------------------------
>
> Key: JBIDE-21972
> URL: https://issues.jboss.org/browse/JBIDE-21972
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
>
> When "Add..." is run on page 'Services & Routing Settings, if list of service ports is not empty, dialog is pre-filled with integers. Some errors should be fixed:
> Case #1
> # ASSERT: have a project in OpenShift
> # EXEC: in Explorer: choose "Deploy Docker Image..." in context menu of your project
> # EXEC: in deploy docker image wizard: pick an image (ex. php),
> # EXEC: confirm the 2nd wizard page ("Deployment Configuration & Scalability") and get to the 3rd wizard page
> # ASSERT: no ports are defined yet
> # EXEC: Create service port=65535, pod port=2000
> # EXEC: Run "Add..." second time.
> Result:
> Service port is filled with 65535 and causes error message.
> Pod port is filled with 65536 also causing error.
> Case #2
> # ASSERT: no ports are defined yet.
> # EXEC: Create service port=2000, pod port=2001
> # EXEC: Run "Add..." second time.
> Result:
> Service port is filled with 2001 - it is ok.
> Pod port is filled with 2001 causing error.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3730) Headless standalone installer can be run with xml config that contains eap bundle
by Jan Richter (JIRA)
Jan Richter created JBDS-3730:
---------------------------------
Summary: Headless standalone installer can be run with xml config that contains eap bundle
Key: JBDS-3730
URL: https://issues.jboss.org/browse/JBDS-3730
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: installer
Affects Versions: 9.1.0.CR1
Reporter: Jan Richter
Assignee: Denis Golovin
Priority: Minor
One can run the headless standalone installer with a config xml file which contains the instructions to install eap as well. This results in the following:
{noformat}[ Starting automated installation ]
[INFO] Selected JVM Information
[INFO] Location : /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.72-1.b15.fc22.x86_64
[INFO] Vendor : Oracle Corporation
[INFO] Version : 1.8.0_72
[INFO] Arch : 64-bit
[ Starting to unpack ]
[ Processing package: P2 Director Application (1/4) ]
[ Processing package: Red Hat JBoss Developer Studio 9.1.0.CR1 (2/4) ]
[ Processing package: Red Hat JBoss Developer Studio 9.1.0.CR1 Metadata Generation (3/4) ]
[ Processing package: JBoss Enterprise Application Platform (4/4) ]
[ WARNING: Error executing
/bin/chmod a+x /home/jrichter/Downloads/temp/runtimes/jboss-eap/bin/init.d/jboss-as-standalone.sh ]
[ ERROR: The installation was not completed ]
[ Unpacking finished ]
com.izforge.izpack.installer.InstallerException: Unpack failed (xml line 19)
com.izforge.izpack.installer.InstallerException: Unpack failed (xml line 19)
at com.izforge.izpack.panels.InstallPanelAutomationHelper.runAutomated(Unknown Source)
at com.izforge.izpack.installer.AutomatedInstaller.installPanel(AutomatedInstaller.java:432)
at com.izforge.izpack.installer.AutomatedInstaller.doInstall(AutomatedInstaller.java:388)
at com.izforge.izpack.installer.Installer.main(Unknown Source)
[ Automated installation FAILED! ]{noformat}
The resulting installation is still perfectly functional, but no icons/shortcuts are created. It might be nicer if the installer was able to identify if it can install all the bundles in the config file and at least warn when starting up.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years