search

felixlu / jap

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

JAP_LOCAL_WS_PYTHON-3.0.0-SNAPSHOT-3 not working on linux #53

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
I tested both "JAP_LOCAL_WS_PYTHON_WINDOWS-3.0.0-SNAPSHOT-3" & 
"JAP_LOCAL_WS_PYTHON-3.0.0-SNAPSHOT-3", the former works OK on windows, the 
later not works on my openSUSE.
I have all the needed componets installed, python, twisted, pyopenssl & 
autobahn, but still show me a "WSOutputProtocolFactory.clientConnectionFailed" 
error

Jeroen, do u have time to look into this?

with regards.

I attach the log here, hoping it will help:
DEBUG:JAP.JAP_LOCAL_WS:WSOutputProtocolFactory.__init__
DEBUG:JAP.JAP_LOCAL:Tunnel.__init__
DEBUG:JAP.JAP_LOCAL:Tunnel.connect
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionLost
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionLost
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionLost
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionLost
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionLost
DEBUG:JAP.JAP_LOCAL_WS:WSOutputProtocolFactory.clientConnectionFailed
DEBUG:JAP.JAP_LOCAL:InputProtocol.outputProtocol_connectionFailed
DEBUG:JAP.JAP_LOCAL_WS:WSOutputProtocolFactory.clientConnectionFailed
DEBUG:JAP.JAP_LOCAL:InputProtocol.outputProtocol_connectionFailed
DEBUG:JAP.JAP_LOCAL_WS:WSOutputProtocolFactory.clientConnectionFailed
DEBUG:JAP.JAP_LOCAL:InputProtocol.outputProtocol_connectionFailed
DEBUG:JAP.JAP_LOCAL_WS:WSInputProtocol.__init__
DEBUG:JAP.JAP_LOCAL:InputProtocol.__init__
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionMade
DEBUG:JAP.JAP_LOCAL_WS:WSOutputProtocolFactory.clientConnectionFailed
DEBUG:JAP.JAP_LOCAL:InputProtocol.outputProtocol_connectionFailed
DEBUG:JAP.JAP_LOCAL_WS:WSOutputProtocolFactory.clientConnectionFailed
DEBUG:JAP.JAP_LOCAL:InputProtocol.outputProtocol_connectionFailed
DEBUG:JAP.JAP_LOCAL:InputProtocol.dataReceived
DEBUG:JAP.JAP_LOCAL:InputProtocol.processDataState0
DEBUG:JAP.JAP_LOCAL:InputProtocol.dataReceived
DEBUG:JAP.JAP_LOCAL:InputProtocol.processDataState1
DEBUG:JAP.JAP_LOCAL:InputProtocol.remoteAddressType: 3
DEBUG:JAP.JAP_LOCAL:InputProtocol.remoteAddress: ssl.gstatic.com
DEBUG:JAP.JAP_LOCAL:InputProtocol.remotePort: 443
DEBUG:JAP.JAP_LOCAL_WS:WSInputProtocol.connect
DEBUG:JAP.JAP_LOCAL_WS:WSOutputProtocolFactory.__init__
DEBUG:JAP.JAP_LOCAL:Tunnel.__init__
DEBUG:JAP.JAP_LOCAL:Tunnel.connect
DEBUG:JAP.JAP_LOCAL_WS:WSInputProtocol.__init__
DEBUG:JAP.JAP_LOCAL:InputProtocol.__init__
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionMade
DEBUG:JAP.JAP_LOCAL:InputProtocol.dataReceived
DEBUG:JAP.JAP_LOCAL:InputProtocol.processDataState0
DEBUG:JAP.JAP_LOCAL:InputProtocol.dataReceived
DEBUG:JAP.JAP_LOCAL:InputProtocol.processDataState1
DEBUG:JAP.JAP_LOCAL:InputProtocol.remoteAddressType: 3
DEBUG:JAP.JAP_LOCAL:InputProtocol.remoteAddress: toolbarqueries.google.com
DEBUG:JAP.JAP_LOCAL:InputProtocol.remotePort: 80
DEBUG:JAP.JAP_LOCAL_WS:WSInputProtocol.connect
DEBUG:JAP.JAP_LOCAL_WS:WSOutputProtocolFactory.__init__
DEBUG:JAP.JAP_LOCAL:Tunnel.__init__
DEBUG:JAP.JAP_LOCAL:Tunnel.connect
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionLost
DEBUG:JAP.JAP_LOCAL_WS:WSOutputProtocolFactory.clientConnectionFailed
DEBUG:JAP.JAP_LOCAL:InputProtocol.outputProtocol_connectionFailed
DEBUG:JAP.JAP_LOCAL_WS:WSInputProtocol.__init__
DEBUG:JAP.JAP_LOCAL:InputProtocol.__init__
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionMade
DEBUG:JAP.JAP_LOCAL:InputProtocol.dataReceived
DEBUG:JAP.JAP_LOCAL:InputProtocol.processDataState0
DEBUG:JAP.JAP_LOCAL:InputProtocol.dataReceived
DEBUG:JAP.JAP_LOCAL:InputProtocol.processDataState1
DEBUG:JAP.JAP_LOCAL:InputProtocol.remoteAddressType: 3
DEBUG:JAP.JAP_LOCAL:InputProtocol.remoteAddress: api.mywot.com
DEBUG:JAP.JAP_LOCAL:InputProtocol.remotePort: 80
DEBUG:JAP.JAP_LOCAL_WS:WSInputProtocol.connect
DEBUG:JAP.JAP_LOCAL_WS:WSOutputProtocolFactory.__init__
DEBUG:JAP.JAP_LOCAL:Tunnel.__init__
DEBUG:JAP.JAP_LOCAL:Tunnel.connect
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionLost
DEBUG:JAP.JAP_LOCAL_WS:WSOutputProtocolFactory.clientConnectionFailed
DEBUG:JAP.JAP_LOCAL:InputProtocol.outputProtocol_connectionFailed
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionLost
DEBUG:JAP.JAP_LOCAL_WS:WSOutputProtocolFactory.clientConnectionFailed
DEBUG:JAP.JAP_LOCAL:InputProtocol.outputProtocol_connectionFailed
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionLost
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionLost
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionLost
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionLost
DEBUG:JAP.JAP_LOCAL_WS:WSOutputProtocolFactory.clientConnectionFailed
DEBUG:JAP.JAP_LOCAL:InputProtocol.outputProtocol_connectionFailed
DEBUG:JAP.JAP_LOCAL_WS:WSOutputProtocolFactory.clientConnectionFailed
DEBUG:JAP.JAP_LOCAL:InputProtocol.outputProtocol_connectionFailed
DEBUG:JAP.JAP_LOCAL_WS:WSOutputProtocolFactory.clientConnectionFailed
DEBUG:JAP.JAP_LOCAL:InputProtocol.outputProtocol_connectionFailed
DEBUG:JAP.JAP_LOCAL_WS:WSOutputProtocolFactory.clientConnectionFailed
DEBUG:JAP.JAP_LOCAL:InputProtocol.outputProtocol_connectionFailed

Original issue reported on code.google.com by fifa...@gmail.com on 27 Jul 2013 at 5:05

GoogleCodeExporter commented 8 years ago 
Can you attach your JAP_LOCAL_WS.json and JAP_REMOTE_WS.json?

Original comment by jeroen.v...@gmail.com on 28 Jul 2013 at 1:23

GoogleCodeExporter commented 8 years ago 
sure, here it is
I have no idea whether it is the DNS problem or something else.
but I could not open any page via JAP on openSUSE, I'm sure it worked before. 
besides, JAP_node works OK on openSUSE when it starts up, then it crashed like 
issue 52

On windows, JAP_LOCAL_WS_PYTHON_WINDOWS-3.0.0-SNAPSHOT-3 works stable till now, 
thanks for your great work :)

Original comment by fifa...@gmail.com on 28 Jul 2013 at 1:45

Attachments:

GoogleCodeExporter commented 8 years ago 
Your configuration looks OK.

Applications on OPENSHIFT are stopped/(re)started when they are idle. To 
restart an idle application you have to send a HTTP request to that application 
(a WEBSOCKET request does not work).
You can send a HTTP request to JAP_REMOTE_WS_PYTHON with your browser: open 
http://ADDRESS or https://ADDRESS

More information: 
https://www.openshift.com/faq/what-happens-if-my-application-is-not-used-for-a-l
ong-time

Did that work?

Original comment by jeroen.v...@gmail.com on 28 Jul 2013 at 2:12

GoogleCodeExporter commented 8 years ago 
Hi Jeroen, I know this limit of openshift :)  I have tried to set CDN to bypass 
this limit and it seems work, so My App on Openshift keeps awake theoretically 
:)
The problem is:
JAP_Python_Openshift works good on windows, all the time, it helped me a lot, 
respects to u:) 
On openSUSE, 3.0.0-SNAPSHOT-3 (surely with the same json config ) not worked 
like his brother, I cannot open any webpage. so strange? maybe it's the problem 
with my openSUSE config? DNS? firewall? python? I have no idea....but JAP_node 
works on openSUSE (at least can open webpages).
I' ll test it on my LinuxMint to confirm this issue, thanks for your reply:)

Original comment by fifa...@gmail.com on 28 Jul 2013 at 2:42

GoogleCodeExporter commented 8 years ago 
Maybe the DNS resolver does not work on LINUX?

In JAP_LOCAL_WS.py, disable the DNS resolver:

#resolver = JAP.JAP_LOCAL.createResolver(configuration)
#reactor.installResolver(resolver)

Did that work?

Original comment by jeroen.v...@gmail.com on 28 Jul 2013 at 3:36

GoogleCodeExporter commented 8 years ago 
yes, it works. after i did this :)

Original comment by fifa...@gmail.com on 28 Jul 2013 at 4:59