[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 commented on JBIDE-21877:
-----------------------------------------------
[~jcantrill], Static method java.net.Authenticator.setDefault(Authenticator) sets the static value that will be used at authentication. Quite a few frameworks may call this method with there own implementation of Authenticator, and we cannot know which one will be the last.
> 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, 2 months
[JBoss JIRA] (JBIDE-21877) Make error message shown in OpenShift Explorer for outdated token more user friendly
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21877?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-21877:
---------------------------------------
[~scabanovich] Can you describe how the proxy authenticator is changed or can be changed. This looks like an issue where we maybe have a proxied connection that is changed (in eclipse pref? system pref?). There were initial tests around proxied connections which shown things to be fine, but maybe we are missing a case here.
[~akazakov] expired token will cause the client to try and reauth...but the NPE is a result of some other issue.
> 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, 2 months
[JBoss JIRA] (TOOLSDOC-719) Document known issue with some linux versions and GTK3: export SWT_GTK3=0
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-719?page=com.atlassian.jira.plug... ]
Nick Boldt updated TOOLSDOC-719:
--------------------------------
Summary: Document known issue with some linux versions and GTK3: export SWT_GTK3=0 (was: Document known issue with some linux versions and GTK3 - SWT_GTK3=0)
> Document known issue with some linux versions and GTK3: export SWT_GTK3=0
> -------------------------------------------------------------------------
>
> Key: TOOLSDOC-719
> URL: https://issues.jboss.org/browse/TOOLSDOC-719
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Feature Request
> Components: General documentation issues, Getting Started Guide
> Affects Versions: 9.1 CR1
> Reporter: Nick Boldt
> Assignee: Misha Ali
> Fix For: 9.1 GA
>
>
> See JBIDE-21038 re: workaround required on some linux distros.
> ---
> Before launching Eclipse or JBDS on linux, ensure your console has run this command:
> {code}export SWT_GTK3=0{code}
> Then start Eclipse or JBDS as you would normally, eg.,
> {code}./eclipse
> or
> ./studio/jbdevstudio
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-21038) Software/Update page is not working on Fedora 23 [JBT 4.3 / Mars]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21038?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-21038:
------------------------------------
Workaround documented here and in TOOLDOC-719. Resolving.
> Software/Update page is not working on Fedora 23 [JBT 4.3 / Mars]
> -----------------------------------------------------------------
>
> Key: JBIDE-21038
> URL: https://issues.jboss.org/browse/JBIDE-21038
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, upstream
> Affects Versions: 4.3.0.Final
> Environment: JBDS 9.0.0.GA
> Reporter: Radim Hopp
> Assignee: Snjezana Peco
> Labels: doc_writer_needed, docs_getting_started_guide, docs_gettingstarted_guide, docs_installation_guide, known_issue
> Fix For: 4.3.1.Final
>
>
> Recently I upgraded my system to Fedora 23 (beta) and second page of Cetnral (Software/Update) is not working. It is rendered with "Refreshing..." text and carousel (which is not spinning as it should). One processor core goes 100%.
> java version "1.8.0_65"
> gtk3 version 3.18.2
> jstack: http://pastebin.com/a7U02yjt
> Everything is fine with GTK2.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-21038) Software/Update page is not working on Fedora 23 [JBT 4.3 / Mars]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21038?page=com.atlassian.jira.plugi... ]
Nick Boldt resolved JBIDE-21038.
--------------------------------
Resolution: Done
> Software/Update page is not working on Fedora 23 [JBT 4.3 / Mars]
> -----------------------------------------------------------------
>
> Key: JBIDE-21038
> URL: https://issues.jboss.org/browse/JBIDE-21038
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, upstream
> Affects Versions: 4.3.0.Final
> Environment: JBDS 9.0.0.GA
> Reporter: Radim Hopp
> Assignee: Snjezana Peco
> Labels: doc_writer_needed, docs_getting_started_guide, docs_gettingstarted_guide, docs_installation_guide, known_issue
> Fix For: 4.3.1.Final
>
>
> Recently I upgraded my system to Fedora 23 (beta) and second page of Cetnral (Software/Update) is not working. It is rendered with "Refreshing..." text and carousel (which is not spinning as it should). One processor core goes 100%.
> java version "1.8.0_65"
> gtk3 version 3.18.2
> jstack: http://pastebin.com/a7U02yjt
> Everything is fine with GTK2.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (TOOLSDOC-719) Document known issue with some linux versions and GTK3 - SWT_GTK3=0
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-719?page=com.atlassian.jira.plug... ]
Nick Boldt updated TOOLSDOC-719:
--------------------------------
Description:
See JBIDE-21038 re: workaround required on some linux distros.
---
Before launching Eclipse or JBDS on linux, ensure your console has run this command:
{code}export SWT_GTK3=0{code}
Then start Eclipse or JBDS as you would normally, eg.,
{code}./eclipse
or
./studio/jbdevstudio
{code}
was:See JBIDE-21038 re: workaround required on some linux distros.
> Document known issue with some linux versions and GTK3 - SWT_GTK3=0
> -------------------------------------------------------------------
>
> Key: TOOLSDOC-719
> URL: https://issues.jboss.org/browse/TOOLSDOC-719
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Feature Request
> Components: General documentation issues, Getting Started Guide
> Affects Versions: 9.1 CR1
> Reporter: Nick Boldt
> Assignee: Misha Ali
> Fix For: 9.1 GA
>
>
> See JBIDE-21038 re: workaround required on some linux distros.
> ---
> Before launching Eclipse or JBDS on linux, ensure your console has run this command:
> {code}export SWT_GTK3=0{code}
> Then start Eclipse or JBDS as you would normally, eg.,
> {code}./eclipse
> or
> ./studio/jbdevstudio
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-21038) Software/Update page is not working on Fedora 23 [JBT 4.3 / Mars]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21038?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-21038:
-------------------------------
Workaround Description:
Before launching Eclipse or JBDS on linux, ensure your console has run this command:
{code}export SWT_GTK3=0{code}
Then start Eclipse or JBDS as you would normally, eg.,
{code}./eclipse
or
./studio/jbdevstudio
{code}
was:
Before launching Eclipse or JBDS on linux, ensure your console has run this command:
{code}export SWT-GTK3=0{code}
Then start Eclipse or JBDS as you would normally, eg.,
{code}./eclipse
or
./studio/jbdevstudio
{code}
> Software/Update page is not working on Fedora 23 [JBT 4.3 / Mars]
> -----------------------------------------------------------------
>
> Key: JBIDE-21038
> URL: https://issues.jboss.org/browse/JBIDE-21038
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, upstream
> Affects Versions: 4.3.0.Final
> Environment: JBDS 9.0.0.GA
> Reporter: Radim Hopp
> Assignee: Snjezana Peco
> Labels: doc_writer_needed, docs_getting_started_guide, docs_gettingstarted_guide, docs_installation_guide, known_issue
> Fix For: 4.3.1.Final
>
>
> Recently I upgraded my system to Fedora 23 (beta) and second page of Cetnral (Software/Update) is not working. It is rendered with "Refreshing..." text and carousel (which is not spinning as it should). One processor core goes 100%.
> java version "1.8.0_65"
> gtk3 version 3.18.2
> jstack: http://pastebin.com/a7U02yjt
> Everything is fine with GTK2.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-21038) Software/Update page is not working on Fedora 23 [JBT 4.3 / Mars]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21038?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-21038:
-------------------------------
Workaround Description:
Before launching Eclipse or JBDS on linux, ensure your console has run this command:
{code}export SWT-GTK3=0{code}
Then start Eclipse or JBDS as you would normally, eg.,
{code}./eclipse
or
./studio/jbdevstudio
{code}
was:
Before launching Eclipse on linux, ensure your console has run this command:
{code}export SWT-GTK3=0{code}
Then start Eclipse or JBDS as you would normally, eg.,
{code}./eclipse
or
./studio/jbdevstudio
{code}
> Software/Update page is not working on Fedora 23 [JBT 4.3 / Mars]
> -----------------------------------------------------------------
>
> Key: JBIDE-21038
> URL: https://issues.jboss.org/browse/JBIDE-21038
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, upstream
> Affects Versions: 4.3.0.Final
> Environment: JBDS 9.0.0.GA
> Reporter: Radim Hopp
> Assignee: Snjezana Peco
> Labels: doc_writer_needed, docs_getting_started_guide, docs_gettingstarted_guide, docs_installation_guide, known_issue
> Fix For: 4.3.1.Final
>
>
> Recently I upgraded my system to Fedora 23 (beta) and second page of Cetnral (Software/Update) is not working. It is rendered with "Refreshing..." text and carousel (which is not spinning as it should). One processor core goes 100%.
> java version "1.8.0_65"
> gtk3 version 3.18.2
> jstack: http://pastebin.com/a7U02yjt
> Everything is fine with GTK2.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-21038) Software/Update page is not working on Fedora 23 [JBT 4.3 / Mars]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21038?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-21038:
-------------------------------
Workaround Description:
Before launching Eclipse on linux, ensure your console has run this command:
{code}export SWT-GTK3=0{code}
Then start Eclipse or JBDS as you would normally, eg.,
{code}./eclipse
or
./studio/jbdevstudio
{code}
Workaround: Workaround Exists
> Software/Update page is not working on Fedora 23 [JBT 4.3 / Mars]
> -----------------------------------------------------------------
>
> Key: JBIDE-21038
> URL: https://issues.jboss.org/browse/JBIDE-21038
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, upstream
> Affects Versions: 4.3.0.Final
> Environment: JBDS 9.0.0.GA
> Reporter: Radim Hopp
> Assignee: Snjezana Peco
> Labels: doc_writer_needed, docs_getting_started_guide, docs_gettingstarted_guide, docs_installation_guide, known_issue
> Fix For: 4.3.1.Final
>
>
> Recently I upgraded my system to Fedora 23 (beta) and second page of Cetnral (Software/Update) is not working. It is rendered with "Refreshing..." text and carousel (which is not spinning as it should). One processor core goes 100%.
> java version "1.8.0_65"
> gtk3 version 3.18.2
> jstack: http://pastebin.com/a7U02yjt
> Everything is fine with GTK2.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months