[JBoss JIRA] (JBDS-3688) Failed to open the Docker explorer
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3688?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov resolved JBDS-3688.
----------------------------------
Fix Version/s: 9.1.0.CR1
Resolution: Cannot Reproduce Bug
> Failed to open the Docker explorer
> ----------------------------------
>
> Key: JBDS-3688
> URL: https://issues.jboss.org/browse/JBDS-3688
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: docker
> Affects Versions: 9.1.0.CR1
> Environment: Windows 10
> JBDS 9.1.0.CR1-v20160318-0804-B422
> Reporter: Fred Bricon
> Assignee: Xavier Coulon
> Fix For: 9.1.0.CR1
>
>
> On Windows 10, after installing JBDS with the CDK v2 Beta5, when opening the docker explorer, an error occurs:
> {noformat}
> !SESSION 2016-03-18 19:13:06.981 -----------------------------------------------
> eclipse.buildId=9.1.0.CR1-v20160318-0804-B422
> java.version=1.8.0_74
> java.vendor=Oracle Corporation
> BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=fr_FR
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -os win32 -ws win32 -arch x86_64 -product com.jboss.devstudio.core.product
> !ENTRY org.eclipse.mylyn.tasks.core 1 0 2016-03-18 19:17:27.066
> !MESSAGE Migrating task repository credentials from keyring.
> !ENTRY org.eclipse.egit.ui 2 0 2016-03-18 19:17:31.467
> !MESSAGE Warning: The environment variable HOME is not set. The following directory will be used to store the Git
> user global configuration and to define the default location to store repositories: 'C:\Users\fbricon'. If this is
> not correct please set the HOME environment variable and restart Eclipse. Otherwise Git for Windows and
> EGit might behave differently since they see different configuration options.
> This warning can be switched off on the Team > Git > Confirmations and Warnings preference page.
> !ENTRY org.jboss.tools.openshift.core 1 0 2016-03-18 19:24:53.273
> !MESSAGE Unauthorized. Trying to reauthenticate
> !ENTRY org.eclipse.osgi 2 0 2016-03-18 19:27:53.577
> !MESSAGE While loading class "org.glassfish.hk2.osgiresourcelocator.ResourceFinder", thread "Thread[Worker-22,5,main]" timed out waiting (5001ms) for thread "Thread[Worker-2,5,main]" to finish starting bundle "org.glassfish.hk2.osgi-resource-locator_2.3.0.b10_v201508191500 [880]". To avoid deadlock, thread "Thread[Worker-22,5,main]" is proceeding but "org.glassfish.hk2.osgiresourcelocator.ResourceFinder" may not be fully initialized.
> !STACK 0
> org.osgi.framework.BundleException: Unable to acquire the state change lock for the module: osgi.identity; osgi.identity="org.glassfish.hk2.osgi-resource-locator"; type="osgi.bundle"; version:Version="2.3.0.b10_v201508191500" [id=880] STARTED [STARTED]
> at org.eclipse.osgi.container.Module.lockStateChange(Module.java:329)
> at org.eclipse.osgi.container.Module.start(Module.java:389)
> at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:454)
> at org.eclipse.osgi.internal.hooks.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107)
> at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:531)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:324)
> at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:327)
> at org.eclipse.osgi.internal.loader.sources.SingleSourcePackage.loadClass(SingleSourcePackage.java:36)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:386)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:352)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:344)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)
> at java.lang.ClassLoader.loadClass(Unknown Source)
> at org.glassfish.jersey.internal.l10n.Localizer.localize(Localizer.java:118)
> at org.glassfish.jersey.client.internal.LocalizationMessages.CLIENT_INSTANCE_CLOSED(LocalizationMessages.java:27)
> at org.glassfish.jersey.client.JerseyClient.checkNotClosed(JerseyClient.java:178)
> at org.glassfish.jersey.client.JerseyClient.target(JerseyClient.java:190)
> 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.info(DefaultDockerClient.java:300)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getInfo(DockerConnection.java:311)
> at org.eclipse.linuxtools.internal.docker.ui.views.ConnectionInfoPropertySection$1.run(ConnectionInfoPropertySection.java:69)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> !ENTRY org.eclipse.osgi 2 0 2016-03-18 19:27:58.725
> !MESSAGE While loading class "org.glassfish.hk2.osgiresourcelocator.ServiceLoader", thread "Thread[Worker-22,5,main]" timed out waiting (5001ms) for thread "Thread[Worker-2,5,main]" to finish starting bundle "org.glassfish.hk2.osgi-resource-locator_2.3.0.b10_v201508191500 [880]". To avoid deadlock, thread "Thread[Worker-22,5,main]" is proceeding but "org.glassfish.hk2.osgiresourcelocator.ServiceLoader" may not be fully initialized.
> !STACK 0
> org.osgi.framework.BundleException: Unable to acquire the state change lock for the module: osgi.identity; osgi.identity="org.glassfish.hk2.osgi-resource-locator"; type="osgi.bundle"; version:Version="2.3.0.b10_v201508191500" [id=880] STARTED [STARTED]
> at org.eclipse.osgi.container.Module.lockStateChange(Module.java:329)
> at org.eclipse.osgi.container.Module.start(Module.java:389)
> at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:454)
> at org.eclipse.osgi.internal.hooks.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107)
> at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:531)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:324)
> at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:327)
> at org.eclipse.osgi.internal.loader.sources.SingleSourcePackage.loadClass(SingleSourcePackage.java:36)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:386)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:352)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:344)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)
> at java.lang.ClassLoader.loadClass(Unknown Source)
> at org.glassfish.hk2.internal.ServiceLocatorFactoryImpl.getOSGiSafeGenerators(ServiceLocatorFactoryImpl.java:103)
> at org.glassfish.hk2.internal.ServiceLocatorFactoryImpl.getGenerator(ServiceLocatorFactoryImpl.java:112)
> at org.glassfish.hk2.internal.ServiceLocatorFactoryImpl.access$000(ServiceLocatorFactoryImpl.java:66)
> at org.glassfish.hk2.internal.ServiceLocatorFactoryImpl$1.run(ServiceLocatorFactoryImpl.java:88)
> at org.glassfish.hk2.internal.ServiceLocatorFactoryImpl$1.run(ServiceLocatorFactoryImpl.java:83)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.glassfish.hk2.internal.ServiceLocatorFactoryImpl.<init>(ServiceLocatorFactoryImpl.java:83)
> at org.glassfish.hk2.api.ServiceLocatorFactory.<clinit>(ServiceLocatorFactory.java:51)
> at org.glassfish.jersey.internal.inject.Injections.<clinit>(Injections.java:68)
> at org.glassfish.jersey.internal.RuntimeDelegateImpl.<init>(RuntimeDelegateImpl.java:61)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
> at java.lang.reflect.Constructor.newInstance(Unknown Source)
> at java.lang.Class.newInstance(Unknown Source)
> at javax.ws.rs.ext.FactoryFinder.newInstance(FactoryFinder.java:118)
> at javax.ws.rs.ext.FactoryFinder.find(FactoryFinder.java:225)
> at javax.ws.rs.ext.RuntimeDelegate.findDelegate(RuntimeDelegate.java:135)
> 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.info(DefaultDockerClient.java:300)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getInfo(DockerConnection.java:311)
> at org.eclipse.linuxtools.internal.docker.ui.views.ConnectionInfoPropertySection$1.run(ConnectionInfoPropertySection.java:69)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> !ENTRY org.eclipse.core.jobs 4 2 2016-03-18 19:27:58.871
> !MESSAGE An internal error occurred during: "Loading connection info...".
> !STACK 0
> 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.info(DefaultDockerClient.java:300)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getInfo(DockerConnection.java:311)
> at org.eclipse.linuxtools.internal.docker.ui.views.ConnectionInfoPropertySection$1.run(ConnectionInfoPropertySection.java:69)
> 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)
> ... 11 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(Unknown Source)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
> at java.lang.reflect.Constructor.newInstance(Unknown Source)
> at java.lang.Class.newInstance(Unknown Source)
> at javax.ws.rs.ext.FactoryFinder.newInstance(FactoryFinder.java:118)
> ... 13 more
> !ENTRY org.eclipse.core.jobs 4 2 2016-03-18 19:27:58.876
> !MESSAGE An internal error occurred during: "Loading containers...".
> !STACK 0
> 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.listContainers(DefaultDockerClient.java:307)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.listContainers(DockerConnection.java:542)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getContainers(DockerConnection.java:435)
> at org.eclipse.linuxtools.internal.docker.ui.views.DockerExplorerContentProvider$1.run(DockerExplorerContentProvider.java:168)
> 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(Unknown Source)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
> at java.lang.reflect.Constructor.newInstance(Unknown Source)
> at java.lang.Class.newInstance(Unknown Source)
> at javax.ws.rs.ext.FactoryFinder.newInstance(FactoryFinder.java:118)
> ... 14 more
> !ENTRY org.eclipse.core.jobs 4 2 2016-03-18 19:29:45.841
> !MESSAGE An internal error occurred during: "Loading connection info...".
> !STACK 0
> 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.info(DefaultDockerClient.java:300)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getInfo(DockerConnection.java:311)
> at org.eclipse.linuxtools.internal.docker.ui.views.ConnectionInfoPropertySection$1.run(ConnectionInfoPropertySection.java:69)
> 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)
> ... 11 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(Unknown Source)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
> at java.lang.reflect.Constructor.newInstance(Unknown Source)
> at java.lang.Class.newInstance(Unknown Source)
> at javax.ws.rs.ext.FactoryFinder.newInstance(FactoryFinder.java:118)
> ... 13 more
> {noformat}
> !http://content.screencast.com/users/fbricon/folders/Jing/media/fe732e1b-a79d-4a7f-85fd-8960e752d2d9/2016-03-18_1932.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-21059) Server Adapter does not connect in debug mode on WF in a Docker container
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21059?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21059:
-----------------------------------
Fix Version/s: 4.4.x
> Server Adapter does not connect in debug mode on WF in a Docker container
> --------------------------------------------------------------------------
>
> Key: JBIDE-21059
> URL: https://issues.jboss.org/browse/JBIDE-21059
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Final
> Reporter: Xavier Coulon
> Assignee: Rob Stryker
> Fix For: 4.4.x
>
>
> I have a WF 9.0.2.Final in a Docker container, started with the debug flag in the command line :
> {code}
> CMD ["/opt/jboss/wildfly/bin/standalone.sh", "-c", "standalone.xml", "-b", "0.0.0.0", "-bmanagement", "0.0.0.0" , "--debug"]
> {code}
> I can connect to this server from the server adapter in Run mode but not in debug mode: the Debug view remains empty and the breakpoints are not hit.
> On the other side, I can connect using the plain Java remote debugger (in the launchers) and the same breakpoints are hit.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-21745) Unable to download EAP 7 Beta runtime using username without "@redhat.com"
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21745?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21745:
-----------------------------------
Fix Version/s: 4.4.0.Alpha1
> Unable to download EAP 7 Beta runtime using username without "@redhat.com"
> --------------------------------------------------------------------------
>
> Key: JBIDE-21745
> URL: https://issues.jboss.org/browse/JBIDE-21745
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.3.0.Final, 4.3.1.CR1
> Environment: JBDS 9.1.0.CR1, JBDS 9.0.0.GA
> Reporter: Radim Hopp
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.4.0.Alpha1
>
>
> Trying to download EAP 7 Beta using login without "@redhat.com" fails on license agreement page.
> Instead of license agreement being displayed, just message saying "It is no longer possible to accept terms and conditions in the wizard. Please, use following link instead!" is shown. Given link redirects to Red Hat Developers portal login. After successful login, message is shown:
> {noformat}
> You Entered All Necessary Information
> Thank you for filling all necessary information. Now you can go back to Eclipse and retry your download of /jboss-eap-7.0.0.Beta.zip.
> {noformat}
> But even after that I'm unable to download that runtime with the same credentials.
> Using login with "@redhat.com" I'm able to download the runtime.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-21953) 10.1.2.2.* not working on Windows from RH network
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21953?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-21953:
--------------------------------------
Assignee: Hardy Ferentschik (was: Martin Malina)
> 10.1.2.2.* not working on Windows from RH network
> -------------------------------------------------
>
> Key: JBIDE-21953
> URL: https://issues.jboss.org/browse/JBIDE-21953
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift, upstream
> Affects Versions: 4.3.1.CR1
> Reporter: Martin Malina
> Assignee: Hardy Ferentschik
> Priority: Critical
> Fix For: 4.4.x
>
>
> This is definitely an upstream issue, but I think it's worth having it here and gather information from others.
> Marian tried openshift with cdk today on our Windows laptop and the url generated for the app he deployed didn't work.
> So I tried something simple like "ping 10.1.2.2.xip.io" from command line and it didn't work.
> "ping xip.io" worked.
> On my OS X laptop, this works as expected:
> {code}
> $ ping 10.1.2.2.xip.io
> PING 10.1.2.2.xip.io (10.1.2.2): 56 data bytes
> Request timeout for icmp_seq 0
> {code}
> Whereas on windows I only get:
> Ping request could not find host 10.1.2.2.xip.io. Please check the name and try again.
> I'm not sure if it's just a problem with our laptop, but it needs investigating in any case.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-21992) Deploy Docker Image wizard: "Deployment Configuration & Scalability" page has minor UI issues
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21992?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21992:
-----------------------------------------------
If this issue is resolved, should be create a new one for missing descriptions?
By the way, there is a common issue with descriptions. If a dialog is not pre-filled and requires user input, then error/cancel message prompting user to do the input usually appears in the message area so that user will know what the page is about only after he puts correct values. :)
> Deploy Docker Image wizard: "Deployment Configuration & Scalability" page has minor UI issues
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-21992
> URL: https://issues.jboss.org/browse/JBIDE-21992
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: deploy_docker_wizard
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
> Attachments: deploy-config-scalability-page.png, deployment-config-page.png, DeploymentConfigLayout.png
>
>
> The ""Deployment Configuration & Scalability" wizard page when deploying a docker image has minor UI glitches that we should fix as you can see in the following screenshot. We should also maybe use 3 groups to distinguish the 3 settings cathegories in more obvious way.
> !deploy-config-scalability-page.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-21992) Deploy Docker Image wizard: "Deployment Configuration & Scalability" page has minor UI issues
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21992?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich edited comment on JBIDE-21992 at 3/30/16 1:41 PM:
------------------------------------------------------------------------
If this issue is resolved, should we create a new one for missing descriptions?
By the way, there is a common issue with descriptions. If a dialog is not pre-filled and requires user input, then error/cancel message prompting user to do the input usually appears in the message area so that user will know what the page is about only after he puts correct values. :)
was (Author: scabanovich):
If this issue is resolved, should be create a new one for missing descriptions?
By the way, there is a common issue with descriptions. If a dialog is not pre-filled and requires user input, then error/cancel message prompting user to do the input usually appears in the message area so that user will know what the page is about only after he puts correct values. :)
> Deploy Docker Image wizard: "Deployment Configuration & Scalability" page has minor UI issues
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-21992
> URL: https://issues.jboss.org/browse/JBIDE-21992
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: deploy_docker_wizard
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
> Attachments: deploy-config-scalability-page.png, deployment-config-page.png, DeploymentConfigLayout.png
>
>
> The ""Deployment Configuration & Scalability" wizard page when deploying a docker image has minor UI glitches that we should fix as you can see in the following screenshot. We should also maybe use 3 groups to distinguish the 3 settings cathegories in more obvious way.
> !deploy-config-scalability-page.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-21953) 10.1.2.2.* not working on Windows from RH network
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21953?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21953:
-----------------------------------
Summary: 10.1.2.2.* not working on Windows from RH network (was: xip.io not working on Windows)
> 10.1.2.2.* not working on Windows from RH network
> -------------------------------------------------
>
> Key: JBIDE-21953
> URL: https://issues.jboss.org/browse/JBIDE-21953
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift, upstream
> Affects Versions: 4.3.1.CR1
> Reporter: Martin Malina
> Assignee: Martin Malina
> Priority: Critical
> Fix For: 4.4.x
>
>
> This is definitely an upstream issue, but I think it's worth having it here and gather information from others.
> Marian tried openshift with cdk today on our Windows laptop and the url generated for the app he deployed didn't work.
> So I tried something simple like "ping 10.1.2.2.xip.io" from command line and it didn't work.
> "ping xip.io" worked.
> On my OS X laptop, this works as expected:
> {code}
> $ ping 10.1.2.2.xip.io
> PING 10.1.2.2.xip.io (10.1.2.2): 56 data bytes
> Request timeout for icmp_seq 0
> {code}
> Whereas on windows I only get:
> Ping request could not find host 10.1.2.2.xip.io. Please check the name and try again.
> I'm not sure if it's just a problem with our laptop, but it needs investigating in any case.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-22005) Unexpected EOF in pod log
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22005?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-22005:
-----------------------------------
Fix Version/s: 4.4.0.Alpha1
> Unexpected EOF in pod log
> -------------------------
>
> Key: JBIDE-22005
> URL: https://issues.jboss.org/browse/JBIDE-22005
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Jeff Cantrill
> Priority: Critical
> Labels: openshift_v3
> Fix For: 4.4.0.Alpha1
>
>
> I had an eap application running on OpenShift. I was watching pod log of the application (stdout from EAP server). Unfortunately in some point console was not enough for displaying pod log and it stopped streaming pod log.
> Last lines from console (output of application pod log)
> {code}
> ...
> [0m[33m09:27:29,845 WARN [org.jgroups.protocols.openshift.KUBE_PING] (Timer-4,shared=tcp) Problem getting Pod json from Kubernetes Client[masterUrl=https://172.30.0.1:443/api/v1, headers={Authorization=#MASKED:885#}, connectTimeout=5000, readTimeout=30000, operationAttempts=3, operationSleep=1000, streamProvider=org.openshift.ping.common.stream.InsecureStreamProvider@4fb96d85] for cluster [hornetq-channel], namespace [serveradaptertrests], labels [application=eap-app]; encountered [java.lang.Exception: 3 attempt(s) with a 1000ms sleep to execute [OpenStream] failed. Last failure was [java.io.IOException: Server returned HTTP response code: 403 for URL: https://172.30.0.1:443/api/v1/namespaces/serveradaptertrests/pods?labelSe...
> error: unexpected EOF
> {code}
> I also checked pod log via Web UI, whether there is something wrong on OpenShift side, but it is tooling related - memory/space for pod log output in console is limited and it went "out of memory". Pod log in Web UI was streaming all the time. This block user from checking pod log once it reach a specific length.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-21953) xip.io not working on Windows
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21953?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21953:
-----------------------------------
Fix Version/s: 4.4.x
> xip.io not working on Windows
> -----------------------------
>
> Key: JBIDE-21953
> URL: https://issues.jboss.org/browse/JBIDE-21953
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift, upstream
> Affects Versions: 4.3.1.CR1
> Reporter: Martin Malina
> Assignee: Martin Malina
> Priority: Critical
> Fix For: 4.4.x
>
>
> This is definitely an upstream issue, but I think it's worth having it here and gather information from others.
> Marian tried openshift with cdk today on our Windows laptop and the url generated for the app he deployed didn't work.
> So I tried something simple like "ping 10.1.2.2.xip.io" from command line and it didn't work.
> "ping xip.io" worked.
> On my OS X laptop, this works as expected:
> {code}
> $ ping 10.1.2.2.xip.io
> PING 10.1.2.2.xip.io (10.1.2.2): 56 data bytes
> Request timeout for icmp_seq 0
> {code}
> Whereas on windows I only get:
> Ping request could not find host 10.1.2.2.xip.io. Please check the name and try again.
> I'm not sure if it's just a problem with our laptop, but it needs investigating in any case.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months