[JBoss JIRA] (JBIDE-21986) Error when opening the "Deploy Docker Image" wizard if no valid Docker connection exists
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-21986:
-------------------------------------
Summary: 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
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, 2 months
[JBoss JIRA] (JBIDE-21947) Docker connection does not work after cdk restart
by Hardy Ferentschik (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21947?page=com.atlassian.jira.plugi... ]
Hardy Ferentschik commented on JBIDE-21947:
-------------------------------------------
{quote}
The linked issue implies it's 0.0.4.1 but is that true?
{quote}
Not sure, no idea how to get _0.0.4.1_, except maybe building from source. I added a comment to the issue that a proper release is needed which also gets published to rubygems to be consumed by the "public".
Personally, I'd like also to get a _1.0.0_ out as part of the CDK 2 final. To me it makes no sense to just increment micro counter and it definitely makes no sense to add yet another level.
Regarding the installer, a new release is required for the CDK either way. The final release of the CDK will need to include an updated version of the vagrant-service-manager gem. I believe the installer uses the gems bundled as part of the CDK zip. So in the end the installer should automatically get the right version of the gem.
Bottom line, afaik there is no consumable release for us atm.
> Docker connection does not work after cdk restart
> -------------------------------------------------
>
> Key: JBIDE-21947
> URL: https://issues.jboss.org/browse/JBIDE-21947
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, upstream
> Affects Versions: 4.3.1.CR1
> Reporter: Martin Malina
> Assignee: Hardy Ferentschik
> Fix For: 4.3.1.CR1
>
>
> When you set up cdk and start it for the first time, docker connection is properly set up and functioning. But when you restart cdk in the servers view, docker connection will no longer work.
> This is caused by a bug in vagrant-service-manager 0.0.4:
> https://github.com/projectatomic/vagrant-service-manager/issues/80
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-21857) Hot class reload doesn't work on OpenShift
by Thomas Mäder (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ]
Thomas Mäder commented on JBIDE-21857:
--------------------------------------
[~maxandersen]: the problem with #5 is that there are references to the old class versions lying around. The IDE correctly tells us that it couldn't do the method change (because relative to the old version of the class, it's still a structural change). I can try to write a Java class that reproduces the problem outside the Wildfly server.
> Hot class reload doesn't work on OpenShift
> ------------------------------------------
>
> Key: JBIDE-21857
> URL: https://issues.jboss.org/browse/JBIDE-21857
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Max Rydahl Andersen
> Priority: Blocker
> Fix For: 4.3.1.CR1
>
>
> When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will :
> - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync
> - will always fail if a method signature changed, the debugger saying JDK is out of sync
> Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server)
> This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBDS-3729) Wrong installer icon and metadata
by Hardy Ferentschik (JIRA)
Hardy Ferentschik created JBDS-3729:
---------------------------------------
Summary: Wrong installer icon and metadata
Key: JBDS-3729
URL: https://issues.jboss.org/browse/JBDS-3729
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: installer
Reporter: Hardy Ferentschik
Attachments: installer-icon.png, installer-meta.png
The installer icon needs styling and the meta information needs to be set properly. See _FileDescription_ and _Company_ in attached screenshot. Also the name of the installer should be adjusted - _Setup-bundled-0.0.2-20160324-_ - it should be the proper product name + a simple version string.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBDS-3728) Assign IDs to UI elements
by Jan Richter (JIRA)
Jan Richter created JBDS-3728:
---------------------------------
Summary: Assign IDs to UI elements
Key: JBDS-3728
URL: https://issues.jboss.org/browse/JBDS-3728
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Components: installer
Reporter: Jan Richter
The use of IDs greatly improves the lookup times and makes automated testing a lot easier. So please do include IDs in elements you create + we should add them to already existing elements that don't have any.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-21985) Unexpected JAX-RS validation error for client filters
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21985?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-21985:
----------------------------------
Labels: jax-rs (was: jax-rs respin-a)
> Unexpected JAX-RS validation error for client filters
> -----------------------------------------------------
>
> Key: JBIDE-21985
> URL: https://issues.jboss.org/browse/JBIDE-21985
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.2.0.Final
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Labels: jax-rs
> Fix For: 4.4.0.Alpha1
>
>
> We are using JAX-RS client filters in our project. One of the classes looks like this:
> ...
> import java.io.IOException;
> import javax.ws.rs.client.ClientRequestContext;
> import javax.ws.rs.client.ClientRequestFilter;
> import javax.ws.rs.ext.Provider;
> ...
> @Provider
> public class ClientFilter implements ClientRequestFilter
> {
> ...
> }
> The class is part of a Dynamic Web Project with JAX-RS support turned on.
> The combination of @Provider and either of the ClientRequestFilter or ClientRequestFilter appears to confuse the JAX-RS validator which produces the following error:
> The Provider must implement at least one of the following interfaces: javax.ws.rs.ext.MessageBodyReader, javax.ws.rs.ext.MessageBodyWriter, javax.ws.rs.ext.ExceptionMapper, javax.ws.rs.ext.ReaderInterceptor, javax.ws.rs.ext.WriterInterceptor, javax.ws.rs.container.ContainerRequestFilter, javax.ws.rs.container.ContainerResponseFilter or javax.ws.rs.ext.ContextResolver.
> I suspect the validator needs to be enhanced to also accept the two client filter interfaces when checking the @Provider annotation?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-21985) Unexpected JAX-RS validation error for client filters
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-21985:
-------------------------------------
Summary: Unexpected JAX-RS validation error for client filters
Key: JBIDE-21985
URL: https://issues.jboss.org/browse/JBIDE-21985
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: webservices
Affects Versions: 4.2.0.Final
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 4.3.1.CR1
We are using JAX-RS client filters in our project. One of the classes looks like this:
...
import java.io.IOException;
import javax.ws.rs.client.ClientRequestContext;
import javax.ws.rs.client.ClientRequestFilter;
import javax.ws.rs.ext.Provider;
...
@Provider
public class ClientFilter implements ClientRequestFilter
{
...
}
The class is part of a Dynamic Web Project with JAX-RS support turned on.
The combination of @Provider and either of the ClientRequestFilter or ClientRequestFilter appears to confuse the JAX-RS validator which produces the following error:
The Provider must implement at least one of the following interfaces: javax.ws.rs.ext.MessageBodyReader, javax.ws.rs.ext.MessageBodyWriter, javax.ws.rs.ext.ExceptionMapper, javax.ws.rs.ext.ReaderInterceptor, javax.ws.rs.ext.WriterInterceptor, javax.ws.rs.container.ContainerRequestFilter, javax.ws.rs.container.ContainerResponseFilter or javax.ws.rs.ext.ContextResolver.
I suspect the validator needs to be enhanced to also accept the two client filter interfaces when checking the @Provider annotation?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-21985) Unexpected JAX-RS validation error for client filters
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21985?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-21985:
----------------------------------
Fix Version/s: 4.4.0.Alpha1
(was: 4.3.1.CR1)
> Unexpected JAX-RS validation error for client filters
> -----------------------------------------------------
>
> Key: JBIDE-21985
> URL: https://issues.jboss.org/browse/JBIDE-21985
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.2.0.Final
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Labels: jax-rs, respin-a
> Fix For: 4.4.0.Alpha1
>
>
> We are using JAX-RS client filters in our project. One of the classes looks like this:
> ...
> import java.io.IOException;
> import javax.ws.rs.client.ClientRequestContext;
> import javax.ws.rs.client.ClientRequestFilter;
> import javax.ws.rs.ext.Provider;
> ...
> @Provider
> public class ClientFilter implements ClientRequestFilter
> {
> ...
> }
> The class is part of a Dynamic Web Project with JAX-RS support turned on.
> The combination of @Provider and either of the ClientRequestFilter or ClientRequestFilter appears to confuse the JAX-RS validator which produces the following error:
> The Provider must implement at least one of the following interfaces: javax.ws.rs.ext.MessageBodyReader, javax.ws.rs.ext.MessageBodyWriter, javax.ws.rs.ext.ExceptionMapper, javax.ws.rs.ext.ReaderInterceptor, javax.ws.rs.ext.WriterInterceptor, javax.ws.rs.container.ContainerRequestFilter, javax.ws.rs.container.ContainerResponseFilter or javax.ws.rs.ext.ContextResolver.
> I suspect the validator needs to be enhanced to also accept the two client filter interfaces when checking the @Provider annotation?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBDS-3627) Installer needs to help move past lack of t/c signing
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBDS-3627?page=com.atlassian.jira.plugin.... ]
Pavol Srna updated JBDS-3627:
-----------------------------
Priority: Blocker (was: Major)
I've raised the priority to blocker since we need at least to tell the user how/where to sign t/c.
> Installer needs to help move past lack of t/c signing
> -----------------------------------------------------
>
> Key: JBDS-3627
> URL: https://issues.jboss.org/browse/JBDS-3627
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Components: installer
> Reporter: Joshua Wilson
> Assignee: Joshua Wilson
> Priority: Blocker
> Labels: havoc
> Fix For: 9.1.0.CR1
>
> Attachments: Installer-not-signed-tc.PNG
>
>
> When you login with an active account that hasn't signed the Terms and Conditions the login fails and tells you why but not how to resolve it.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months