[JBoss JIRA] (JBIDE-22009) Rsync failure at server startup
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-22009:
-------------------------------------
Summary: Rsync failure at server startup
Key: JBIDE-22009
URL: https://issues.jboss.org/browse/JBIDE-22009
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.CR1
Reporter: Xavier Coulon
Once the server adapter (auto)starts when I get the following error message in my console:
{code}
receiving file list ... done
ROOT.war.deployed
sent 60 bytes received 228 bytes 115.20 bytes/sec
total size is 8498388 speedup is 29508.29
rsync: delete_file: rmdir "/Users/xcoulon/workspaces/runtime-Eclipse-mars.2/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample(a)eap-app/deploy/ROOT.war" failed: Directory not empty (66)
rsync error: some files could not be transferred (code 23) at /SourceCache/rsync/rsync-45/rsync/main.c(1400) [generator=2.6.9]
error: exit status 23
{code}
from CLI, I can actually confirm that the {{ROOT.war}} directory exists and is not empty.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21983) RuntimeException when trying to see Docker containers/images
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21983?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21983:
-----------------------------------
Component/s: upstream
> 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, upstream
> 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, 1 month
[JBoss JIRA] (JBIDE-21992) Deploy Docker Image wizard: "Deployment Configuration & Scalability" page has minor UI issues
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21992?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-21992:
----------------------------------------
Yes please create a separate issue.
> 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, 1 month
[JBoss JIRA] (JBIDE-21859) Collect usage on LiveReload
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21859?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-21859:
----------------------------------------
I may remember it wrong but c=0 means the usage counted 0 events. So it won't report it. I don't know why it's 0. Need to investigate.
> Collect usage on LiveReload
> ---------------------------
>
> Key: JBIDE-21859
> URL: https://issues.jboss.org/browse/JBIDE-21859
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: livereload
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Priority: Critical
> Fix For: 4.3.1.CR1
>
>
> Measure number of installations, LiveReload server starts and maybe even number of requests, grouped by day.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21877) Make error message shown in OpenShift Explorer for outdated token more user friendly
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21877?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich edited comment on JBIDE-21877 at 3/30/16 4:33 PM:
------------------------------------------------------------------------
[~jcantrill], some org.eclipse.epp.internal.mpc.core.MarketplaceClientCorePlugin at start calls ProxyHelper.acquireProxyService() which sets that evil ProxyHelper.ProxyAuthenticator as the default authenticator. It remembers the previous authenticator, and is ready to restore it when it finds no proxies - but here NPE because of missing requestingURL prevents that. So, I think, we can in OpenShiftCredentialsProvider override SystemDefaultCredentialsProvider so that it would call Authenticator.requestPasswordAuthentication with non-null URL, actually any, just localhost, then ProxyAuthenticator will find no proxies and turn to 'delegate' - that is previous authenticator replaced by epp.
And actually, they at epp.mpc just one month ago fixed another NPE in that class (see https://bugs.eclipse.org/bugs/show_bug.cgi?id=487975, https://github.com/eclipse/epp.mpc/commit/130d33d3cfd152635be4ab9f876b633...). Maybe we can kindly ask themto fix this one too.
was (Author: scabanovich):
[~jcantrill], some org.eclipse.epp.internal.mpc.core.MarketplaceClientCorePlugin at start calls ProxyHelper.acquireProxyService() which sets that evil ProxyHelper.ProxyAuthenticator as the default authenticator. It remembers the previous authenticator, and is ready to restore it when it finds no proxies - but here NPE because of missing requestingURL prevents that. So, I think, we can in OpenShiftCredentialsProvider override SystemDefaultCredentialsProvider so that it would call Authenticator.requestPasswordAuthentication with non-null URL, actually any, just localhost, then ProxyAuthenticator will find no proxies and turn to 'delegate' - that is previous authenticator replaced by epp.
And actually, they at epp.mpc jjust one month ago fixed another NPE in that class (see epp.mpc, https://github.com/eclipse/epp.mpc/commit/130d33d3cfd152635be4ab9f876b633...). Maybe we can kindly ask themto fix this one too.
> Make error message shown in OpenShift Explorer for outdated token more user friendly
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-21877
> URL: https://issues.jboss.org/browse/JBIDE-21877
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: connection, openshift_v3
> Fix For: 4.4.0.Alpha1
>
>
> When I am trying to connect to OpenShift connection with outdated token stored in secure storage, an error tree item is shown in OpenShift Explorer under the connection. Erro tree item is "java.lang.NullPointerException", but it could be something more user friendly such as "Expired credentials" or the one we are already using in other scenarious - You must obtain an API token by .... Following stack trace is in error log
> {code}
> There was an error retrieving children in the OpenShift explorer
> java.lang.NullPointerException
> at org.eclipse.epp.internal.mpc.core.util.ProxyHelper$ProxyAuthenticator.getPasswordAuthentication(ProxyHelper.java:124)
> at java.net.Authenticator.requestPasswordAuthentication(Authenticator.java:317)
> at org.apache.http.impl.client.SystemDefaultCredentialsProvider.getSystemCreds(SystemDefaultCredentialsProvider.java:92)
> at org.apache.http.impl.client.SystemDefaultCredentialsProvider.getCredentials(SystemDefaultCredentialsProvider.java:113)
> at com.openshift.internal.restclient.authorization.OpenShiftCredentialsProvider.getCredentials(OpenShiftCredentialsProvider.java:69)
> at org.apache.http.impl.client.AuthenticationStrategyImpl.select(AuthenticationStrategyImpl.java:184)
> at org.apache.http.impl.client.TargetAuthenticationStrategy.select(TargetAuthenticationStrategy.java:43)
> at org.apache.http.impl.auth.HttpAuthenticator.handleAuthChallenge(HttpAuthenticator.java:154)
> at org.apache.http.impl.execchain.MainClientExec.needAuthentication(MainClientExec.java:557)
> at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:275)
> at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195)
> at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86)
> at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108)
> at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106)
> at com.openshift.internal.restclient.authorization.AuthorizationClient.getContextUsingCredentials(AuthorizationClient.java:134)
> at com.openshift.internal.restclient.authorization.AuthorizationClient.getContext(AuthorizationClient.java:99)
> at com.openshift.internal.restclient.DefaultClient.getContext(DefaultClient.java:504)
> at org.jboss.tools.openshift.core.connection.Connection.authorize(Connection.java:236)
> at org.jboss.tools.openshift.core.connection.Connection.connect(Connection.java:226)
> at org.jboss.tools.openshift.core.connection.Connection.retryList(Connection.java:445)
> at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:389)
> at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:376)
> at org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectCache.getProjectsFor(OpenShiftProjectCache.java:59)
> at org.jboss.tools.openshift.internal.ui.explorer.OpenShiftExplorerContentProvider.getChildrenFor(OpenShiftExplorerContentProvider.java:93)
> at org.jboss.tools.openshift.internal.common.ui.explorer.BaseExplorerContentProvider$1.run(BaseExplorerContentProvider.java:167)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21877) Make error message shown in OpenShift Explorer for outdated token more user friendly
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21877?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich edited comment on JBIDE-21877 at 3/30/16 4:32 PM:
------------------------------------------------------------------------
[~jcantrill], some org.eclipse.epp.internal.mpc.core.MarketplaceClientCorePlugin at start calls ProxyHelper.acquireProxyService() which sets that evil ProxyHelper.ProxyAuthenticator as the default authenticator. It remembers the previous authenticator, and is ready to restore it when it finds no proxies - but here NPE because of missing requestingURL prevents that. So, I think, we can in OpenShiftCredentialsProvider override SystemDefaultCredentialsProvider so that it would call Authenticator.requestPasswordAuthentication with non-null URL, actually any, just localhost, then ProxyAuthenticator will find no proxies and turn to 'delegate' - that is previous authenticator replaced by epp.
And actually, they at epp.mpc jjust one month ago fixed another NPE in that class (see epp.mpc, https://github.com/eclipse/epp.mpc/commit/130d33d3cfd152635be4ab9f876b633...). Maybe we can kindly ask themto fix this one too.
was (Author: scabanovich):
[~jcantrill], some org.eclipse.epp.internal.mpc.core.MarketplaceClientCorePlugin at start calls ProxyHelper.acquireProxyService() which sets that evil ProxyHelper.ProxyAuthenticator as the default authenticator. It remembers the previous authenticator, and is ready to restore it when it finds no proxies - but here NPE because of missing requestingURL prevents that. So, I think, we can in OpenShiftCredentialsProvider override SystemDefaultCredentialsProvider so that it would call Authenticator.requestPasswordAuthentication with non-null URL, actually any, just localhost, then ProxyAuthenticator will find no proxies and turn to 'delegate' - that is previous authenticator replaced by epp.
> Make error message shown in OpenShift Explorer for outdated token more user friendly
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-21877
> URL: https://issues.jboss.org/browse/JBIDE-21877
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: connection, openshift_v3
> Fix For: 4.4.0.Alpha1
>
>
> When I am trying to connect to OpenShift connection with outdated token stored in secure storage, an error tree item is shown in OpenShift Explorer under the connection. Erro tree item is "java.lang.NullPointerException", but it could be something more user friendly such as "Expired credentials" or the one we are already using in other scenarious - You must obtain an API token by .... Following stack trace is in error log
> {code}
> There was an error retrieving children in the OpenShift explorer
> java.lang.NullPointerException
> at org.eclipse.epp.internal.mpc.core.util.ProxyHelper$ProxyAuthenticator.getPasswordAuthentication(ProxyHelper.java:124)
> at java.net.Authenticator.requestPasswordAuthentication(Authenticator.java:317)
> at org.apache.http.impl.client.SystemDefaultCredentialsProvider.getSystemCreds(SystemDefaultCredentialsProvider.java:92)
> at org.apache.http.impl.client.SystemDefaultCredentialsProvider.getCredentials(SystemDefaultCredentialsProvider.java:113)
> at com.openshift.internal.restclient.authorization.OpenShiftCredentialsProvider.getCredentials(OpenShiftCredentialsProvider.java:69)
> at org.apache.http.impl.client.AuthenticationStrategyImpl.select(AuthenticationStrategyImpl.java:184)
> at org.apache.http.impl.client.TargetAuthenticationStrategy.select(TargetAuthenticationStrategy.java:43)
> at org.apache.http.impl.auth.HttpAuthenticator.handleAuthChallenge(HttpAuthenticator.java:154)
> at org.apache.http.impl.execchain.MainClientExec.needAuthentication(MainClientExec.java:557)
> at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:275)
> at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195)
> at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86)
> at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108)
> at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106)
> at com.openshift.internal.restclient.authorization.AuthorizationClient.getContextUsingCredentials(AuthorizationClient.java:134)
> at com.openshift.internal.restclient.authorization.AuthorizationClient.getContext(AuthorizationClient.java:99)
> at com.openshift.internal.restclient.DefaultClient.getContext(DefaultClient.java:504)
> at org.jboss.tools.openshift.core.connection.Connection.authorize(Connection.java:236)
> at org.jboss.tools.openshift.core.connection.Connection.connect(Connection.java:226)
> at org.jboss.tools.openshift.core.connection.Connection.retryList(Connection.java:445)
> at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:389)
> at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:376)
> at org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectCache.getProjectsFor(OpenShiftProjectCache.java:59)
> at org.jboss.tools.openshift.internal.ui.explorer.OpenShiftExplorerContentProvider.getChildrenFor(OpenShiftExplorerContentProvider.java:93)
> at org.jboss.tools.openshift.internal.common.ui.explorer.BaseExplorerContentProvider$1.run(BaseExplorerContentProvider.java:167)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month