[jbosstools-issues] [JBoss JIRA] (JBIDE-25263) OSIO Error refreshing token

[Andre Dietisheim (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-25263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13478599#comment-13478599 ] 

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 at 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)