[JBoss JIRA] (JBIDE-25263) OSIO Error refreshing token
by Lucia Jelinkova (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25263?page=com.atlassian.jira.plugi... ]
Lucia Jelinkova commented on JBIDE-25263:
-----------------------------------------
Sorry, no steps. One day it worked and the other did not.
One strange thing that my colleague [~rhopp] spot was that the exception contained IAccount where access token and refresh token were the same. He thinks they should be different.
> OSIO Error refreshing token
> ---------------------------
>
> Key: JBIDE-25263
> URL: https://issues.jboss.org/browse/JBIDE-25263
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.5.1.AM3
> Reporter: Lucia Jelinkova
> Labels: OSIO
> Fix For: 4.5.x
>
>
> When I called the OSIO service from Fabric8 plugin, the following error occurred.
> {code:java}
> org.jboss.tools.openshift.io.core.exception.OpenshiftIORefreshException: Error refreshing token for ljelinko(a)redhat.com on cluster OpenShift.io
> at org.jboss.tools.openshift.io.core.AccountService.performRefresh(AccountService.java:168)
> at org.jboss.tools.openshift.io.core.AccountService.getToken(AccountService.java:101)
> at org.jboss.tools.openshift.io.internal.core.DefaultTokenProvider.apply(DefaultTokenProvider.java:24)
> at org.jboss.tools.openshift.io.internal.core.DefaultTokenProvider.apply(DefaultTokenProvider.java:1)
> at com.redhat.fabric8analytics.lsp.eclipse.ui.TokenCheck.getToken(TokenCheck.java:60)
> at com.redhat.fabric8analytics.lsp.eclipse.ui.Fabric8AnalyticsStreamConnectionProvider.checkPreferences(Fabric8AnalyticsStreamConnectionProvider.java:67)
> at com.redhat.fabric8analytics.lsp.eclipse.ui.Fabric8AnalyticsStreamConnectionProvider.<init>(Fabric8AnalyticsStreamConnectionProvider.java:54)
> 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 org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:184)
> at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905)
> at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
> at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
> at org.eclipse.lsp4e.LanguageServersRegistry$ExtensionLanguageServerDefinition.createConnectionProvider(LanguageServersRegistry.java:102)
> at org.eclipse.lsp4e.ProjectSpecificLanguageServerWrapper.<init>(ProjectSpecificLanguageServerWrapper.java:142)
> at org.eclipse.lsp4e.LanguageServiceAccessor.getLSWrapperForConnection(LanguageServiceAccessor.java:199)
> at org.eclipse.lsp4e.LanguageServiceAccessor.getLSWrappers(LanguageServiceAccessor.java:163)
> at org.eclipse.lsp4e.LanguageServiceAccessor.getLSPDocumentInfosFor(LanguageServiceAccessor.java:261)
> at org.eclipse.lsp4e.ConnectDocumentToLanguageServerSetupParticipant$1.run(ConnectDocumentToLanguageServerSetupParticipant.java:74)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> {code}
> Well, I can see from the code that there was some unexpected response from OSIO server but it would be helpful if you could provide some more information, at least the server's true response code. In this case the user is absolutely clueless as what happend.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBIDE-25263) OSIO Error refreshing token
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25263?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-25263:
------------------------------------------
[~ljelinko] reading your latter analysis result where you discover the 401 makes me think that this is a bug. Any chance that you'd find out steps to reproduce it?
> OSIO Error refreshing token
> ---------------------------
>
> Key: JBIDE-25263
> URL: https://issues.jboss.org/browse/JBIDE-25263
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.5.1.AM3
> Reporter: Lucia Jelinkova
> Labels: OSIO
> Fix For: 4.5.x
>
>
> When I called the OSIO service from Fabric8 plugin, the following error occurred.
> {code:java}
> org.jboss.tools.openshift.io.core.exception.OpenshiftIORefreshException: Error refreshing token for ljelinko(a)redhat.com on cluster OpenShift.io
> at org.jboss.tools.openshift.io.core.AccountService.performRefresh(AccountService.java:168)
> at org.jboss.tools.openshift.io.core.AccountService.getToken(AccountService.java:101)
> at org.jboss.tools.openshift.io.internal.core.DefaultTokenProvider.apply(DefaultTokenProvider.java:24)
> at org.jboss.tools.openshift.io.internal.core.DefaultTokenProvider.apply(DefaultTokenProvider.java:1)
> at com.redhat.fabric8analytics.lsp.eclipse.ui.TokenCheck.getToken(TokenCheck.java:60)
> at com.redhat.fabric8analytics.lsp.eclipse.ui.Fabric8AnalyticsStreamConnectionProvider.checkPreferences(Fabric8AnalyticsStreamConnectionProvider.java:67)
> at com.redhat.fabric8analytics.lsp.eclipse.ui.Fabric8AnalyticsStreamConnectionProvider.<init>(Fabric8AnalyticsStreamConnectionProvider.java:54)
> 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 org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:184)
> at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905)
> at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
> at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
> at org.eclipse.lsp4e.LanguageServersRegistry$ExtensionLanguageServerDefinition.createConnectionProvider(LanguageServersRegistry.java:102)
> at org.eclipse.lsp4e.ProjectSpecificLanguageServerWrapper.<init>(ProjectSpecificLanguageServerWrapper.java:142)
> at org.eclipse.lsp4e.LanguageServiceAccessor.getLSWrapperForConnection(LanguageServiceAccessor.java:199)
> at org.eclipse.lsp4e.LanguageServiceAccessor.getLSWrappers(LanguageServiceAccessor.java:163)
> at org.eclipse.lsp4e.LanguageServiceAccessor.getLSPDocumentInfosFor(LanguageServiceAccessor.java:261)
> at org.eclipse.lsp4e.ConnectDocumentToLanguageServerSetupParticipant$1.run(ConnectDocumentToLanguageServerSetupParticipant.java:74)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> {code}
> Well, I can see from the code that there was some unexpected response from OSIO server but it would be helpful if you could provide some more information, at least the server's true response code. In this case the user is absolutely clueless as what happend.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBIDE-25263) OSIO Error refreshing token
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25263?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25263:
-------------------------------------
Labels: OSIO (was: )
> OSIO Error refreshing token
> ---------------------------
>
> Key: JBIDE-25263
> URL: https://issues.jboss.org/browse/JBIDE-25263
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.5.1.AM3
> Reporter: Lucia Jelinkova
> Labels: OSIO
> Fix For: 4.5.x
>
>
> When I called the OSIO service from Fabric8 plugin, the following error occurred.
> {code:java}
> org.jboss.tools.openshift.io.core.exception.OpenshiftIORefreshException: Error refreshing token for ljelinko(a)redhat.com on cluster OpenShift.io
> at org.jboss.tools.openshift.io.core.AccountService.performRefresh(AccountService.java:168)
> at org.jboss.tools.openshift.io.core.AccountService.getToken(AccountService.java:101)
> at org.jboss.tools.openshift.io.internal.core.DefaultTokenProvider.apply(DefaultTokenProvider.java:24)
> at org.jboss.tools.openshift.io.internal.core.DefaultTokenProvider.apply(DefaultTokenProvider.java:1)
> at com.redhat.fabric8analytics.lsp.eclipse.ui.TokenCheck.getToken(TokenCheck.java:60)
> at com.redhat.fabric8analytics.lsp.eclipse.ui.Fabric8AnalyticsStreamConnectionProvider.checkPreferences(Fabric8AnalyticsStreamConnectionProvider.java:67)
> at com.redhat.fabric8analytics.lsp.eclipse.ui.Fabric8AnalyticsStreamConnectionProvider.<init>(Fabric8AnalyticsStreamConnectionProvider.java:54)
> 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 org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:184)
> at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905)
> at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
> at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
> at org.eclipse.lsp4e.LanguageServersRegistry$ExtensionLanguageServerDefinition.createConnectionProvider(LanguageServersRegistry.java:102)
> at org.eclipse.lsp4e.ProjectSpecificLanguageServerWrapper.<init>(ProjectSpecificLanguageServerWrapper.java:142)
> at org.eclipse.lsp4e.LanguageServiceAccessor.getLSWrapperForConnection(LanguageServiceAccessor.java:199)
> at org.eclipse.lsp4e.LanguageServiceAccessor.getLSWrappers(LanguageServiceAccessor.java:163)
> at org.eclipse.lsp4e.LanguageServiceAccessor.getLSPDocumentInfosFor(LanguageServiceAccessor.java:261)
> at org.eclipse.lsp4e.ConnectDocumentToLanguageServerSetupParticipant$1.run(ConnectDocumentToLanguageServerSetupParticipant.java:74)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> {code}
> Well, I can see from the code that there was some unexpected response from OSIO server but it would be helpful if you could provide some more information, at least the server's true response code. In this case the user is absolutely clueless as what happend.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBIDE-25263) OSIO Error refreshing token
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25263?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25263:
-------------------------------------
Fix Version/s: 4.5.x
> OSIO Error refreshing token
> ---------------------------
>
> Key: JBIDE-25263
> URL: https://issues.jboss.org/browse/JBIDE-25263
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.5.1.AM3
> Reporter: Lucia Jelinkova
> Labels: OSIO
> Fix For: 4.5.x
>
>
> When I called the OSIO service from Fabric8 plugin, the following error occurred.
> {code:java}
> org.jboss.tools.openshift.io.core.exception.OpenshiftIORefreshException: Error refreshing token for ljelinko(a)redhat.com on cluster OpenShift.io
> at org.jboss.tools.openshift.io.core.AccountService.performRefresh(AccountService.java:168)
> at org.jboss.tools.openshift.io.core.AccountService.getToken(AccountService.java:101)
> at org.jboss.tools.openshift.io.internal.core.DefaultTokenProvider.apply(DefaultTokenProvider.java:24)
> at org.jboss.tools.openshift.io.internal.core.DefaultTokenProvider.apply(DefaultTokenProvider.java:1)
> at com.redhat.fabric8analytics.lsp.eclipse.ui.TokenCheck.getToken(TokenCheck.java:60)
> at com.redhat.fabric8analytics.lsp.eclipse.ui.Fabric8AnalyticsStreamConnectionProvider.checkPreferences(Fabric8AnalyticsStreamConnectionProvider.java:67)
> at com.redhat.fabric8analytics.lsp.eclipse.ui.Fabric8AnalyticsStreamConnectionProvider.<init>(Fabric8AnalyticsStreamConnectionProvider.java:54)
> 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 org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:184)
> at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905)
> at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
> at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
> at org.eclipse.lsp4e.LanguageServersRegistry$ExtensionLanguageServerDefinition.createConnectionProvider(LanguageServersRegistry.java:102)
> at org.eclipse.lsp4e.ProjectSpecificLanguageServerWrapper.<init>(ProjectSpecificLanguageServerWrapper.java:142)
> at org.eclipse.lsp4e.LanguageServiceAccessor.getLSWrapperForConnection(LanguageServiceAccessor.java:199)
> at org.eclipse.lsp4e.LanguageServiceAccessor.getLSWrappers(LanguageServiceAccessor.java:163)
> at org.eclipse.lsp4e.LanguageServiceAccessor.getLSPDocumentInfosFor(LanguageServiceAccessor.java:261)
> at org.eclipse.lsp4e.ConnectDocumentToLanguageServerSetupParticipant$1.run(ConnectDocumentToLanguageServerSetupParticipant.java:74)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> {code}
> Well, I can see from the code that there was some unexpected response from OSIO server but it would be helpful if you could provide some more information, at least the server's true response code. In this case the user is absolutely clueless as what happend.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBIDE-25011) sometimes ITests fail to resolve nexus content from 10.8.243.80:8081/nexus
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25011?page=com.atlassian.jira.plugi... ]
Pavol Srna commented on JBIDE-25011:
------------------------------------
10.8.243.80:8081 is the nexus mirror installed in CCI. In fact it is a CCI VM that runs nexus and the reason behind is to speed up the builds. There is a custom settings.xml you can set for your job to use the mirror. If you do not set the settings.xml for your job, then the default is repository.jboss.org.
Sometimes it happens that the content is not yet synced or some other error happens occasionally.
I believe I can close this jira as won't fix. Please reopen if you feel otherwise. Thx.
> sometimes ITests fail to resolve nexus content from 10.8.243.80:8081/nexus
> --------------------------------------------------------------------------
>
> Key: JBIDE-25011
> URL: https://issues.jboss.org/browse/JBIDE-25011
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: integration-tests
> Affects Versions: 4.5.1.AM2
> Reporter: Nick Boldt
> Assignee: Pavol Srna
> Fix For: 4.5.1.Final
>
>
> {code}
> 16:49:57 Downloading: http://10.8.243.80:8081/nexus/content/repositories/jboss-nexus-public-jbo...
> 16:49:57
> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> 16:49:57 [FATAL] Non-resolvable parent POM for org.jboss.tools:central.maven.examples:4.4.3-SNAPSHOT: Could not transfer artifact org.jboss.tools:parent:pom:4.5.1.AM1-SNAPSHOT from/to jbosstools-base (${jbosstools-base-site}): Cannot access ${jbosstools-base-site} with type p2 using the available connector factories: BasicRepositoryConnectorFactory and 'parent.relativePath' points at wrong local POM @ line 5, column 10
> 16:49:57 @
> 16:49:57 [ERROR] The build could not read 1 project -> [Help 1]
> 16:49:57 [ERROR]
> 16:49:57 [ERROR] The project org.jboss.tools:central.maven.examples:4.4.3-SNAPSHOT (/mnt/hudson_workspace/workspace/examples.prcheck/jdk/openjdk-1.8/label/rhel7/jbosstools-central/pom.xml) has 1 error
> 16:49:57 [ERROR] Non-resolvable parent POM for org.jboss.tools:central.maven.examples:4.4.3-SNAPSHOT: Could not transfer artifact org.jboss.tools:parent:pom:4.5.1.AM1-SNAPSHOT from/to jbosstools-base (${jbosstools-base-site}): Cannot access ${jbosstools-base-site} with type p2 using the available connector factories: BasicRepositoryConnectorFactory and 'parent.relativePath' points at wrong local POM @ line 5, column 10: Cannot access ${jbosstools-base-site} with type p2 using the available layout factories: Maven2RepositoryLayoutFactory: Unsupported repository layout p2 -> [Help 2]{code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples...
> Is there a reason why these jobs are configured to use *10.8.243.80:8081/nexus* instead of simply *repository.jboss.org/nexus* or *origin-repository.jboss.org/nexus* ?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBIDE-25011) sometimes ITests fail to resolve nexus content from 10.8.243.80:8081/nexus
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25011?page=com.atlassian.jira.plugi... ]
Pavol Srna resolved JBIDE-25011.
--------------------------------
Fix Version/s: 4.5.1.Final
(was: 4.5.x)
Resolution: Won't Fix
> sometimes ITests fail to resolve nexus content from 10.8.243.80:8081/nexus
> --------------------------------------------------------------------------
>
> Key: JBIDE-25011
> URL: https://issues.jboss.org/browse/JBIDE-25011
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: integration-tests
> Affects Versions: 4.5.1.AM2
> Reporter: Nick Boldt
> Assignee: Pavol Srna
> Fix For: 4.5.1.Final
>
>
> {code}
> 16:49:57 Downloading: http://10.8.243.80:8081/nexus/content/repositories/jboss-nexus-public-jbo...
> 16:49:57
> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> 16:49:57 [FATAL] Non-resolvable parent POM for org.jboss.tools:central.maven.examples:4.4.3-SNAPSHOT: Could not transfer artifact org.jboss.tools:parent:pom:4.5.1.AM1-SNAPSHOT from/to jbosstools-base (${jbosstools-base-site}): Cannot access ${jbosstools-base-site} with type p2 using the available connector factories: BasicRepositoryConnectorFactory and 'parent.relativePath' points at wrong local POM @ line 5, column 10
> 16:49:57 @
> 16:49:57 [ERROR] The build could not read 1 project -> [Help 1]
> 16:49:57 [ERROR]
> 16:49:57 [ERROR] The project org.jboss.tools:central.maven.examples:4.4.3-SNAPSHOT (/mnt/hudson_workspace/workspace/examples.prcheck/jdk/openjdk-1.8/label/rhel7/jbosstools-central/pom.xml) has 1 error
> 16:49:57 [ERROR] Non-resolvable parent POM for org.jboss.tools:central.maven.examples:4.4.3-SNAPSHOT: Could not transfer artifact org.jboss.tools:parent:pom:4.5.1.AM1-SNAPSHOT from/to jbosstools-base (${jbosstools-base-site}): Cannot access ${jbosstools-base-site} with type p2 using the available connector factories: BasicRepositoryConnectorFactory and 'parent.relativePath' points at wrong local POM @ line 5, column 10: Cannot access ${jbosstools-base-site} with type p2 using the available layout factories: Maven2RepositoryLayoutFactory: Unsupported repository layout p2 -> [Help 2]{code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples...
> Is there a reason why these jobs are configured to use *10.8.243.80:8081/nexus* instead of simply *repository.jboss.org/nexus* or *origin-repository.jboss.org/nexus* ?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months