search

felixlu / jap

Automatically exported from code.google.com/p/jap
0 stars 0 forks source link

Openshift activation problem #28

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1.deploy JAP on Openshift successfully and remove local certificate setting in 
Issues 27.
2.without any connection for some time,maybe tow days. 
3.use it again.

What is the expected output? What do you see instead?
famous 'connectionlost' again

What version of the product are you using? On what operating system?
1.Remote:JAP_WS_REMOTE_PYTHON_OPENSHIFT-2.0.0-SNAPSHOT-3
2.Local:JAP_WS_LOCAL_PYTHON-2.0.0-SNAPSHOT-2-TEST
3.OS:Archlinux + Xfce4.10 + Chromium

Please provide any additional information below.
My correction method is first to open my https://YYY-ZZZ.rhcloud.com:8443 
without any proxy,and then run JAP.
It seems Openshift server is sleeping so have to open the project homepage to 
activate it.

Original issue reported on code.google.com by westmin...@gmail.com on 5 Feb 2013 at 11:15

GoogleCodeExporter commented 8 years ago 
Thanks for the information :)

Original comment by jeroen.v...@gmail.com on 6 Feb 2013 at 9:57

GoogleCodeExporter commented 8 years ago 
I thought Openshift server will sleep without any connection for a few days. 
However, these weeks I found out even I'm using the proxy, Openshift would 
suddenly refuse to work, showing me 503 error in the browser. I have to 
directly connect to the app's address in a terminal via curl or w3m or any 
other tool. After successful connection, JAP proxy will be back to work again.
I don't know if Openshift or JAP causes this problem. My wordpress app running 
in Openshift with the other account does not have this inactivation issue. And 
In ".openshift/action_hooks/start" I find this code 'source 
"${OPENSHIFT_VIRTUALENV_DIR}/bin/activate"'. Is it the related code?

Original comment by westmin...@gmail.com on 13 Apr 2013 at 10:45

GoogleCodeExporter commented 8 years ago 
I do not know. OPENSHIFT websockets use port 8000 and 8443. Maybe OPENSHIFT is 
not configured to reactivate applications on those ports?

BTW, I have released a UI for JAP: JAP_PYTHON.
Can you test?

Original comment by jeroen.v...@gmail.com on 15 Apr 2013 at 7:16