[jbosstools-issues] [JBoss JIRA] (JBIDE-11445) Cannot create application

Andre Dietisheim (JIRA) jira-events at lists.jboss.org
Tue Apr 3 06:40:47 EDT 2012


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

Andre Dietisheim commented on JBIDE-11445:
------------------------------------------

with the new client jar I still have issues when creating applications:

!cannot-create-application.png!

In the log I see the following:

{quote}
com.openshift.express.client.OpenShiftEndpointException: Could not configure application "as2" at "https://openshift.redhat.com/broker/cartridge"
	at com.openshift.express.client.OpenShiftService.sendRequest(OpenShiftService.java:526)
	at com.openshift.express.client.OpenShiftService.requestApplicationAction(OpenShiftService.java:435)
	at com.openshift.express.client.OpenShiftService.createApplication(OpenShiftService.java:290)
	at com.openshift.express.client.OpenShiftService.createApplication(OpenShiftService.java:191)
	at com.openshift.express.internal.client.InternalUser.createApplication(InternalUser.java:197)
	at org.jboss.tools.openshift.express.internal.core.console.UserDelegate.createApplication(UserDelegate.java:117)
	at org.jboss.tools.openshift.express.internal.ui.wizard.OpenShiftExpressApplicationWizardModel$1.call(OpenShiftExpressApplicationWizardModel.java:370)
	at org.jboss.tools.openshift.express.internal.ui.wizard.OpenShiftExpressApplicationWizardModel$1.call(OpenShiftExpressApplicationWizardModel.java:1)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:662)
Caused by: java.net.SocketTimeoutException: Read timed out
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
	at sun.net.www.protocol.http.HttpURLConnection$6.run(HttpURLConnection.java:1491)
	at java.security.AccessController.doPrivileged(Native Method)
	at sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.java:1485)
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1139)
	at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:379)
	at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:318)
	at com.openshift.express.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:103)
	at com.openshift.express.internal.client.httpclient.UrlConnectionHttpClient.post(UrlConnectionHttpClient.java:75)
	at com.openshift.express.client.OpenShiftService.sendRequest(OpenShiftService.java:517)
	... 12 more
Caused by: java.net.SocketTimeoutException: Read timed out
	at java.net.SocketInputStream.socketRead0(Native Method)
	at java.net.SocketInputStream.read(SocketInputStream.java:129)
	at com.sun.net.ssl.internal.ssl.InputRecord.readFully(InputRecord.java:293)
	at com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:331)
	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:798)
	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:755)
	at com.sun.net.ssl.internal.ssl.AppInputStream.read(AppInputStream.java:75)
	at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
	at java.io.BufferedInputStream.read1(BufferedInputStream.java:258)
	at java.io.BufferedInputStream.read(BufferedInputStream.java:317)
	at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:695)
	at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:640)
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1195)
	at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:234)
	at com.openshift.express.internal.client.httpclient.UrlConnectionHttpClient.post(UrlConnectionHttpClient.java:70)
	... 13 more

!ENTRY org.jboss.tools.openshift.express.ui 4 0 2012-04-03 12:35:57.721
!MESSAGE Could not create application "as2"
!STACK 0
com.openshift.express.client.OpenShiftException: Failed to create application: Could not configure application "as2" at "https://openshift.redhat.com/broker/cartridge"
	at org.jboss.tools.openshift.express.internal.ui.wizard.OpenShiftExpressApplicationWizardModel.createApplication(OpenShiftExpressApplicationWizardModel.java:390)
	at org.jboss.tools.openshift.express.internal.ui.wizard.OpenShiftExpressApplicationWizardModel.createApplication(OpenShiftExpressApplicationWizardModel.java:398)
	at org.jboss.tools.openshift.express.internal.ui.wizard.OpenShiftExpressApplicationWizard$3.run(OpenShiftExpressApplicationWizard.java:179)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
{quote}

To me there's now an issue with the way timeouts are reported. They dont make it to the UI any longer. We need to fix that.
                
> Cannot create application
> -------------------------
>
>                 Key: JBIDE-11445
>                 URL: https://issues.jboss.org/browse/JBIDE-11445
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 3.3.0.Beta3
>            Reporter: Andre Dietisheim
>            Assignee: Andre Dietisheim
>            Priority: Critical
>             Fix For: 3.3.0.Beta3
>
>         Attachments: not-supported-for-generic-application.png
>
>
> When creating a new application with the current tooling against the current production server of OpemShift you get the following error:

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jbosstools-issues mailing list