[JBoss JIRA] (JBIDE-20072) Explorer, Connection wizard: Connection refused exception is not clearly presented to the user
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20072?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-20072:
-------------------------------------
Labels: openshift_v3 (was: )
> Explorer, Connection wizard: Connection refused exception is not clearly presented to the user
> ----------------------------------------------------------------------------------------------
>
> Key: JBIDE-20072
> URL: https://issues.jboss.org/browse/JBIDE-20072
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Jeff Cantrill
> Labels: openshift_v3
> Fix For: 4.3.0.CR1
>
> Attachments: Exception.png
>
>
> Trying to connect using an existing connection to a server that is not available does not display nice to the user and the console logs show:
> {code}
> com.openshift.restclient.OpenShiftException: Exception getting the resource
> at com.openshift.internal.restclient.DefaultClient.handleHttpClientException(DefaultClient.java:396)
> at com.openshift.internal.restclient.DefaultClient.get(DefaultClient.java:241)
> at com.openshift.internal.restclient.DefaultClient.getCurrentUser(DefaultClient.java:402)
> at com.openshift.internal.restclient.authorization.AuthorizationClient.getContext(AuthorizationClient.java:93)
> at com.openshift.internal.restclient.DefaultClient.getContext(DefaultClient.java:407)
> at org.jboss.tools.openshift.core.connection.Connection.authorize(Connection.java:210)
> at org.jboss.tools.openshift.core.connection.Connection.connect(Connection.java:200)
> at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPageModel.connect(ConnectionWizardPageModel.java:263)
> at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPage$ConnectJob.doRun(ConnectionWizardPage.java:335)
> at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: com.openshift.internal.restclient.http.HttpClientException: java.net.ConnectException: Connection refused
> at com.openshift.internal.restclient.http.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:217)
> at com.openshift.internal.restclient.http.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:151)
> at com.openshift.internal.restclient.http.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:130)
> at com.openshift.internal.restclient.http.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:92)
> at com.openshift.internal.restclient.DefaultClient.getVersion(DefaultClient.java:307)
> at com.openshift.internal.restclient.DefaultClient.getOpenShiftVersions(DefaultClient.java:283)
> at com.openshift.internal.restclient.DefaultClient.getOpenShiftAPIVersion(DefaultClient.java:297)
> at com.openshift.internal.restclient.DefaultClient.getTypeMappings(DefaultClient.java:332)
> at com.openshift.internal.restclient.DefaultClient.get(DefaultClient.java:232)
> ... 9 more
> Caused by: java.net.ConnectException: Connection refused
> 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:422)
> at sun.net.www.protocol.http.HttpURLConnection$10.run(HttpURLConnection.java:1889)
> at sun.net.www.protocol.http.HttpURLConnection$10.run(HttpURLConnection.java:1884)
> at java.security.AccessController.doPrivileged(Native Method)
> at sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.java:1883)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1456)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1440)
> at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480)
> at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338)
> at com.openshift.internal.restclient.http.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:200)
> ... 17 more
> Caused by: java.net.ConnectException: Connection refused
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345)
> at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
> at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> at java.net.Socket.connect(Socket.java:589)
> at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:656)
> at sun.security.ssl.BaseSSLSocketImpl.connect(BaseSSLSocketImpl.java:173)
> at sun.net.NetworkClient.doConnect(NetworkClient.java:180)
> at sun.net.www.http.HttpClient.openServer(HttpClient.java:432)
> at sun.net.www.http.HttpClient.openServer(HttpClient.java:527)
> at sun.net.www.protocol.https.HttpsClient.<init>(HttpsClient.java:275)
> at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:371)
> at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:191)
> at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1104)
> at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:998)
> at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:177)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1512)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1440)
> at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)
> at com.openshift.internal.restclient.http.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:147)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-20107) Browser connects on port 8080 instead of livereload custom port
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-20107:
-------------------------------------
Summary: Browser connects on port 8080 instead of livereload custom port
Key: JBIDE-20107
URL: https://issues.jboss.org/browse/JBIDE-20107
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: livereload
Affects Versions: 4.3.0.Alpha2
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Priority: Critical
When selecting a module and calling {{Show In>Web browser via LiveReload}}, the browser connects on the default HTTP port of the app server instead of connecting on the LiveReload custom port (something like {{54321}}.
Digging with curl, it seems that the URL used to connect does not contain a trailing '/' and in return, WildFly responds with a {{302}} response and a new location which passes through the 8080 port:
{code}
curl -v http://192.168.0.10:55201/conferenceschedule
* Hostname was NOT found in DNS cache
* Trying 192.168.0.10...
* Connected to 192.168.0.10 (192.168.0.10) port 55201 (#0)
> GET /conferenceschedule HTTP/1.1
> User-Agent: curl/7.37.1
> Host: 192.168.0.10:55201
> Accept: */*
>
< HTTP/1.1 302 Found
< Date: Wed, 17 Jun 2015 14:55:33 GMT
< X-Powered-By: Undertow/1
* Server WildFly/8 is not blacklisted
< Server: WildFly/8
< Location: http://192.168.59.103:8080/conferenceschedule/
< Date: Wed, 17 Jun 2015 14:55:33 GMT
< Content-Length: 0
<
* Connection #0 to host 192.168.0.10 left intact
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-20054) Connection wizard: Cannot remove secure storage of v3 connection token
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20054?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-20054:
-------------------------------------
Priority: Critical (was: Major)
> Connection wizard: Cannot remove secure storage of v3 connection token
> ----------------------------------------------------------------------
>
> Key: JBIDE-20054
> URL: https://issues.jboss.org/browse/JBIDE-20054
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Marián Labuda
> Assignee: Max Rydahl Andersen
> Priority: Critical
> Labels: openshift_v3
> Fix For: 4.3.0.Beta2
>
>
> If I create a new v3 connection with OAuth authentization method and choose to store token in secure storage (or I edit the existing one connection with token and check the checkbox to store the token in secure storage), token is stored. But if I decide later to prevent it to being stored by unchecking the checkbox in Edit connection dialog, it does not work. If I uncheck the checbox and hit the Finish button and come back to edit connection dialog, the checkbox is still checked. This is related only to OAuth authentization method (basic authentization method works as expected).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-20072) Connection refused exception is not clearly presented to the user
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20072?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-20072:
-------------------------------------
Fix Version/s: 4.3.0.CR1
(was: 4.3.0.Beta2)
> Connection refused exception is not clearly presented to the user
> -----------------------------------------------------------------
>
> Key: JBIDE-20072
> URL: https://issues.jboss.org/browse/JBIDE-20072
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Jeff Cantrill
> Fix For: 4.3.0.CR1
>
> Attachments: Exception.png
>
>
> Trying to connect using an existing connection to a server that is not available does not display nice to the user and the console logs show:
> {code}
> com.openshift.restclient.OpenShiftException: Exception getting the resource
> at com.openshift.internal.restclient.DefaultClient.handleHttpClientException(DefaultClient.java:396)
> at com.openshift.internal.restclient.DefaultClient.get(DefaultClient.java:241)
> at com.openshift.internal.restclient.DefaultClient.getCurrentUser(DefaultClient.java:402)
> at com.openshift.internal.restclient.authorization.AuthorizationClient.getContext(AuthorizationClient.java:93)
> at com.openshift.internal.restclient.DefaultClient.getContext(DefaultClient.java:407)
> at org.jboss.tools.openshift.core.connection.Connection.authorize(Connection.java:210)
> at org.jboss.tools.openshift.core.connection.Connection.connect(Connection.java:200)
> at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPageModel.connect(ConnectionWizardPageModel.java:263)
> at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPage$ConnectJob.doRun(ConnectionWizardPage.java:335)
> at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: com.openshift.internal.restclient.http.HttpClientException: java.net.ConnectException: Connection refused
> at com.openshift.internal.restclient.http.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:217)
> at com.openshift.internal.restclient.http.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:151)
> at com.openshift.internal.restclient.http.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:130)
> at com.openshift.internal.restclient.http.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:92)
> at com.openshift.internal.restclient.DefaultClient.getVersion(DefaultClient.java:307)
> at com.openshift.internal.restclient.DefaultClient.getOpenShiftVersions(DefaultClient.java:283)
> at com.openshift.internal.restclient.DefaultClient.getOpenShiftAPIVersion(DefaultClient.java:297)
> at com.openshift.internal.restclient.DefaultClient.getTypeMappings(DefaultClient.java:332)
> at com.openshift.internal.restclient.DefaultClient.get(DefaultClient.java:232)
> ... 9 more
> Caused by: java.net.ConnectException: Connection refused
> 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:422)
> at sun.net.www.protocol.http.HttpURLConnection$10.run(HttpURLConnection.java:1889)
> at sun.net.www.protocol.http.HttpURLConnection$10.run(HttpURLConnection.java:1884)
> at java.security.AccessController.doPrivileged(Native Method)
> at sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.java:1883)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1456)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1440)
> at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480)
> at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338)
> at com.openshift.internal.restclient.http.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:200)
> ... 17 more
> Caused by: java.net.ConnectException: Connection refused
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345)
> at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
> at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> at java.net.Socket.connect(Socket.java:589)
> at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:656)
> at sun.security.ssl.BaseSSLSocketImpl.connect(BaseSSLSocketImpl.java:173)
> at sun.net.NetworkClient.doConnect(NetworkClient.java:180)
> at sun.net.www.http.HttpClient.openServer(HttpClient.java:432)
> at sun.net.www.http.HttpClient.openServer(HttpClient.java:527)
> at sun.net.www.protocol.https.HttpsClient.<init>(HttpsClient.java:275)
> at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:371)
> at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:191)
> at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1104)
> at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:998)
> at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:177)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1512)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1440)
> at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)
> at com.openshift.internal.restclient.http.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:147)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-20054) Cannot remove secure storage of v3 connection token
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20054?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-20054:
-------------------------------------
Priority: Major (was: Minor)
> Cannot remove secure storage of v3 connection token
> ---------------------------------------------------
>
> Key: JBIDE-20054
> URL: https://issues.jboss.org/browse/JBIDE-20054
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Marián Labuda
> Assignee: Max Rydahl Andersen
> Labels: openshift_v3
> Fix For: 4.3.0.Beta2
>
>
> If I create a new v3 connection with OAuth authentization method and choose to store token in secure storage (or I edit the existing one connection with token and check the checkbox to store the token in secure storage), token is stored. But if I decide later to prevent it to being stored by unchecking the checkbox in Edit connection dialog, it does not work. If I uncheck the checbox and hit the Finish button and come back to edit connection dialog, the checkbox is still checked. This is related only to OAuth authentization method (basic authentization method works as expected).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-20054) Cannot remove secure storage of v3 connection token
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20054?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-20054:
-------------------------------------
Labels: openshift_v3 (was: )
> Cannot remove secure storage of v3 connection token
> ---------------------------------------------------
>
> Key: JBIDE-20054
> URL: https://issues.jboss.org/browse/JBIDE-20054
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Marián Labuda
> Assignee: Max Rydahl Andersen
> Labels: openshift_v3
> Fix For: 4.3.0.Beta2
>
>
> If I create a new v3 connection with OAuth authentization method and choose to store token in secure storage (or I edit the existing one connection with token and check the checkbox to store the token in secure storage), token is stored. But if I decide later to prevent it to being stored by unchecking the checkbox in Edit connection dialog, it does not work. If I uncheck the checbox and hit the Finish button and come back to edit connection dialog, the checkbox is still checked. This is related only to OAuth authentization method (basic authentization method works as expected).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-20054) Connection wizard: Cannot remove secure storage of v3 connection token
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20054?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-20054:
-------------------------------------
Summary: Connection wizard: Cannot remove secure storage of v3 connection token (was: Cannot remove secure storage of v3 connection token)
> Connection wizard: Cannot remove secure storage of v3 connection token
> ----------------------------------------------------------------------
>
> Key: JBIDE-20054
> URL: https://issues.jboss.org/browse/JBIDE-20054
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Marián Labuda
> Assignee: Max Rydahl Andersen
> Labels: openshift_v3
> Fix For: 4.3.0.Beta2
>
>
> If I create a new v3 connection with OAuth authentization method and choose to store token in secure storage (or I edit the existing one connection with token and check the checkbox to store the token in secure storage), token is stored. But if I decide later to prevent it to being stored by unchecking the checkbox in Edit connection dialog, it does not work. If I uncheck the checbox and hit the Finish button and come back to edit connection dialog, the checkbox is still checked. This is related only to OAuth authentization method (basic authentization method works as expected).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-20047) As I user I want to be able to manually trigger builds
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20047?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-20047:
-------------------------------------
Fix Version/s: 4.3.x
(was: 4.3.0.Beta2)
> As I user I want to be able to manually trigger builds
> ------------------------------------------------------
>
> Key: JBIDE-20047
> URL: https://issues.jboss.org/browse/JBIDE-20047
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Fix For: 4.3.x
>
>
> In STI a build is triggered by a change in the git repository. As a user I can thus triggered a build via a git push given that the git repo has the webhook installed. If I dont have the webhooks installed and I'm maybe not able to install them I'd like to be able to manually trigger the build.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-20047) As I user I want to be able to manually trigger builds
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20047?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-20047:
------------------------------------------
Postponing this to 4.3.x. [~maxandersen] agree?
> As I user I want to be able to manually trigger builds
> ------------------------------------------------------
>
> Key: JBIDE-20047
> URL: https://issues.jboss.org/browse/JBIDE-20047
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Fix For: 4.3.x
>
>
> In STI a build is triggered by a change in the git repository. As a user I can thus triggered a build via a git push given that the git repo has the webhook installed. If I dont have the webhooks installed and I'm maybe not able to install them I'd like to be able to manually trigger the build.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months