bug of "JAP_REMOTE_WS_NODE_NODEJITSU-3.0.0-SNAPSHOT-2"?

felixlu / jap

Automatically exported from code.google.com/p/jap

0 stars 0 forks source link

bug of "JAP_REMOTE_WS_NODE_NODEJITSU-3.0.0-SNAPSHOT-2"? #52

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago

I deployed the latest version on nodejitsu, modulus & openshift
Modulus & Openshift seems OK till now (not test thoroughly), when using 
nodejitsu, JAP crashed with this debug info (reproduced several times ):

remoteConnection.message
remoteConnection.message: messageLength=303
remoteConnection.message
remoteConnection.message: messageLength=0
remoteConnection.message
remoteConnection.message: messageLength=303
remoteConnection.message
remoteConnection.message: messageLength=0
remoteConnection.message
remoteConnection.message: messageLength=0
remoteConnection.message
remoteConnection.message: messageLength=304
remoteConnection.message
remoteConnection.message: messageLength=0
remoteConnection.message
remoteConnection.message: messageLength=305

events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: read ECONNRESET
    at errnoException (net.js:901:11)
    at TCP.onread (net.js:556:19)

Original issue reported on code.google.com by dellajon...@gmail.com on 27 Jul 2013 at 12:06

GoogleCodeExporter commented 8 years ago

Thanks for the report!
I will try to reproduce the error.

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

GoogleCodeExporter commented 8 years ago

further report :
the problem is also with modulus & openshift
have been using JAP_REMOTE_WS_NODE_XXXX-3.0.0-SNAPSHOT for a while, seemed 
enough stable.

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

GoogleCodeExporter commented 8 years ago

Probably because the new release uses a new WEBSOCKET library.

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

GoogleCodeExporter commented 8 years ago

I think the bug is related to https://github.com/einaros/ws/pull/105
So I have updated https://github.com/jvansteirteghem/streamws

Can you reinstall JAP_LOCAL_WS_NODE and JAP_REMOTE_WS_NODE and test?
(NM.bat installs https://github.com/jvansteirteghem/streamws)

Also, what is your NODE version (possible bug? 
https://groups.google.com/forum/#!topic/nodejs/Sc-_U-aoMsU)?

Original comment by jeroen.v...@gmail.com on 29 Jul 2013 at 6:34

GoogleCodeExporter commented 8 years ago

URL: https://groups.google.com/forum/#!topic/nodejs/Sc-_U-aoMsU

Original comment by jeroen.v...@gmail.com on 29 Jul 2013 at 6:36

GoogleCodeExporter commented 8 years ago

after update streamws, no crash happens.
I have been always keep NODE to the latest version
so it's the new WS libary bug not the NODE problem
I will test it some days to ensure this:)

Original comment by fifa...@gmail.com on 29 Jul 2013 at 11:28

GoogleCodeExporter commented 8 years ago

Thanks :)

Original comment by jeroen.v...@gmail.com on 30 Jul 2013 at 12:18

GoogleCodeExporter commented 8 years ago

Can you help me? 
How to install streamws in XP? I have download the zip of streamws.
Thanks

Original comment by yscad...@gmail.com on 18 Aug 2014 at 2:43