unnivm / jwebsocket

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

JWebSocket server drops connections for the test clients loaded from the same system #171

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Start the jWebSocket server on a Windows 7 or Ubuntu 10.4 host
2. Load the index.html that comes with the jWebsocket client package
3. Go to the 'Hello world' demo and try to login

What is the expected output? What do you see instead?
I expect to see this output on the client console (like what I get when I try 
the Demo on the jWebSocket.org website):
Connecting to ws://jwebsocket.org:8787/jWebSocket/jWebSocket and logging in as 
'root'...
Ok
jWebSocket connection established.
jWebSocket Welcome received.
jWebSocket 'welcome' token received, full message: 
'{"anonymous":true,"username":"anonymous","ns":"org.jwebsocket.plugins.system","
protocolVersion":13,"vendor":"jWebSocket.org","type":"welcome","timeout":0,"sour
ceId":"01.5590.1756","usid":"c18244830395ecb85f4ab232491a39df","version":"1.0b4 
(nightly build 11201)"}' 
jWebSocket 'response' token received, full message: 
'{"username":"root","ns":"org.jwebsocket.plugins.system","utid":1,"reqType":"log
in","code":0,"type":"response","msg":"ok","sourceId":"01.5590.1756"}'

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

Please provide any additional information below.
The server tells me that the connection has been dropped because of handshake 
issues.

Original issue reported on code.google.com by vichargr...@gmail.com on 6 Apr 2012 at 1:05

GoogleCodeExporter commented 9 years ago
One more thing, the <domain> section has entries for localhost and 127.0.0.1 
which comes with.  I also added entries for 127.0.0.1:8787 (default listening 
port for the server) and <server IP>:8787.  These <domain> directives do not 
help.

Original comment by vichargr...@gmail.com on 6 Apr 2012 at 1:08

GoogleCodeExporter commented 9 years ago
OK I just saw the workaround for this in issue 166.  Thanks.  

Original comment by vichargr...@gmail.com on 6 Apr 2012 at 9:48