[jbosstools-issues] [JBoss JIRA] (JBIDE-15835) Timeout when add/remove postgresql cartridge to application (Openshift Enterprise)
Marián Labuda created JBIDE-15835:
-------------------------------------
Summary: Timeout when add/remove postgresql cartridge to application
(Openshift Enterprise)
Key: JBIDE-15835
URL: https://issues.jboss.org/browse/JBIDE-15835
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.1.1.Beta1
Reporter: Marián Labuda
Assignee: Andre Dietisheim
Attempt to add to existing (or can be added when creating new) application PostgreSQL
database cartridge cause connection time out. Dialog with text
{code}Could not request url
https://console.itos.redhat.com/broker/rest/domains/domainequo2/applicati...,
connection timed out {code} is shown.
Finally, cartridge seems to be added correctly (seems to be embedded well, environment
variables are correctly set up for the given cartridge etc.)
This happens only on Openshift Enterprise (Openshift Online works fine)
Eclipse log:
{code}
!ENTRY org.jboss.tools.openshift.express.ui 4 0 2013-11-01 12:54:14.209
!MESSAGE Could not embed cartridges for application dasda
!STACK 0
com.openshift.client.OpenShiftTimeoutException: Could not request url
https://console.itos.redhat.com/broker/rest/domains/domainequo2/applicati...,
connection timed out
at com.openshift.internal.client.RestService.request(RestService.java:139)
at com.openshift.internal.client.RestService.request(RestService.java:109)
at com.openshift.internal.client.RestService.request(RestService.java:92)
at
com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:142)
at
com.openshift.internal.client.ApplicationResource$AddEmbeddedCartridgeRequest.execute(ApplicationResource.java:1026)
at
com.openshift.internal.client.ApplicationResource.addEmbeddableCartridge(ApplicationResource.java:353)
at
com.openshift.internal.client.ApplicationResource.addEmbeddableCartridges(ApplicationResource.java:368)
at
org.jboss.tools.openshift.express.internal.ui.job.EmbedCartridgesJob.addEmbeddedCartridges(EmbedCartridgesJob.java:94)
at
org.jboss.tools.openshift.express.internal.ui.job.EmbedCartridgesJob.doRun(EmbedCartridgesJob.java:56)
at
org.jboss.tools.openshift.express.internal.ui.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:150)
at java.net.SocketInputStream.read(SocketInputStream.java:121)
at sun.security.ssl.InputRecord.readFully(InputRecord.java:442)
at sun.security.ssl.InputRecord.read(InputRecord.java:480)
at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:927)
at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:884)
at sun.security.ssl.AppInputStream.read(AppInputStream.java:102)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:235)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:275)
at java.io.BufferedInputStream.read(BufferedInputStream.java:334)
at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:633)
at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:579)
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1322)
at
sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)
at
com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:146)
at
com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:125)
at
com.openshift.internal.client.httpclient.UrlConnectionHttpClient.post(UrlConnectionHttpClient.java:101)
at com.openshift.internal.client.RestService.request(RestService.java:179)
at com.openshift.internal.client.RestService.request(RestService.java:123)
... 10 more
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira