search

felixlu / jap

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

jap via openshift ,it don't work #34

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1.I deployed jap in openshift, everything is ok,i can use it,but after two 
days, chrome ERROR 120(net::ERR_SOCKS_CONNECTION_FAILED), I landed 
openshift.redhat.com to restart the app.Then Return to normal，how to solve 
this problem。
2.
3.

What is the expected output? What do you see instead?
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.inputProtocol_connectionLost
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.onClose
DEBUG:JAP.JAP_LOCAL:InputProtocol.outputProtocol_connectionLost
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionLost
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.inputProtocol_connectionLost
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.onClose
DEBUG:JAP.JAP_LOCAL:InputProtocol.outputProtocol_connectionLost
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionLost
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.inputProtocol_connectionLost
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.__init__
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.__init__
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.onOpen
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.onClose
DEBUG:JAP.JAP_LOCAL:InputProtocol.outputProtocol_connectionLost
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionLost
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.inputProtocol_connectionLost
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.onOpen
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.onClose
DEBUG:JAP.JAP_LOCAL:InputProtocol.outputProtocol_connectionLost
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionLost
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.inputProtocol_connectionLost

What version of the product are you using? On what operating system?

JAP_WS_LOCAL_PYTHON_WINDOWS-2.0.0-SNAPSHOT-2
JAP_WS_REMOTE_PYTHON_OPENSHIFT-2.0.0-SNAPSHOT-3
windows 7 64bit    chrome 24.0.1312.56 

Please provide any additional information below.

Original issue reported on code.google.com by lingd...@gmail.com on 1 Mar 2013 at 2:35

GoogleCodeExporter commented 8 years ago 
I also have that problem.
I reactivate the application by opening http://XXX-YYY.rhcloud.com/ in a 
browser.
I think you cannot reactivate the application on port 8000 or 8443 (ports for 
experimental websocket support).

Original comment by jeroen.v...@gmail.com on 1 Mar 2013 at 2:51