[
https://issues.jboss.org/browse/JBIDE-10675?page=com.atlassian.jira.plugi...
]
Andre Dietisheim edited comment on JBIDE-10675 at 1/19/12 3:54 PM:
-------------------------------------------------------------------
It turns out that the client get a 404 when the DNS-name starts to become available.
There's no body to the response though and that's where the java client gets an
NPE.
Talking to the OpenShift dev team, we found out that it was the proxy that caused the 404.
The current java client considers the app to be available as soon as the app is responding
on its DNS name. This is not reliable, the rhc-tools do also consider the response code. I
filed this to JBIDE-10676.
was (Author: adietish):
It turns out that the client get a 404 when the DNS-name starts to become available.
There's no body to the response though and that's where the java client gets an
NPE.
NPE when creating an application in the staging environment
-----------------------------------------------------------
Key: JBIDE-10675
URL:
https://issues.jboss.org/browse/JBIDE-10675
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 3.3.0.M5
Environment: openshift express staging environment
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 3.3.0.Beta1
--
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