Kris <kborcher@redhat.com> made a comment on bug 1005373
Here is the description from the related JIRA:
We have discovered an issue where our OpenShift instance seems to stop responding to any requests on port 8443. We are using SockJS and browsers that do not support WebSocket will fallback to other protocols will use the same port, 8443 in our case.
We have disabled WebSocket support on this OpenShift application/gear. This was created using the following command:
There is a demo web app that can be used to to access the above server by setting the sockjs_url to point to the server mentioned above.
This issue does not seem to happen upon every request, but does happen quite frequently. When the instance stops responding a way to make it start responding again is to telnet to it from the OpenShift gear/instance itself:
telnet localhost 8000
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
GET /simplepush HTTP/1.1
HOST bogus.com
After this it will work again until it gets "stuck" again.
Sorry for the vague description but this is all I have a the moment.
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
Kris <kborcher@redhat.com> made a comment on bug 1005373
Here is the description from the related JIRA:
We have discovered an issue where our OpenShift instance seems to stop responding to any requests on port 8443. We are using SockJS and browsers that do not support WebSocket will fallback to other protocols will use the same port, 8443 in our case.
We have disabled WebSocket support on this OpenShift application/gear. This was created using the following command:
rhc create-app timeout "https://cartreflect-claytondev.rhcloud.com/reflect?github=danbev/openshift-origin-cartridge-aerogear-push&commit=2aa85a3015db85961e8bf7b32d6cc9b57156aa4a" mysql-5.1
There is a demo web app that can be used to to access the above server by setting the sockjs_url to point to the server mentioned above.
This issue does not seem to happen upon every request, but does happen quite frequently. When the instance stops responding a way to make it start responding again is to telnet to it from the OpenShift gear/instance itself:
telnet localhost 8000
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
GET /simplepush HTTP/1.1
HOST bogus.com
After this it will work again until it gets "stuck" again.
Sorry for the vague description but this is all I have a the moment.