[
https://issues.jboss.org/browse/ISPN-943?page=com.atlassian.jira.plugin.s...
]
Galder Zamarreño commented on ISPN-943:
---------------------------------------
Actually, after further trying, in spite of errors or anything in the console, I'm
being able to trace the javascript.
It appears that the Websocket is not open (websocket.readyState == WebSocket.OPEN returns
false), even though
http://localhost:8181/infinispan-ws.js is responding, so all the
messages are being queued and not sent.
That would explain why the server log shows no incoming requests at all.
Websocket demo not working
--------------------------
Key: ISPN-943
URL:
https://issues.jboss.org/browse/ISPN-943
Project: Infinispan
Issue Type: Bug
Affects Versions: 4.2.0.Final, 4.2.1.CR3
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 4.2.1.FINAL
From Burr:
"I am trying to build a websocket prototype/demo. That means I am looking at things
like Jetty, Resin and Kaazing. AND I would love it if I could just make the demo work
with Infinispan - since the final demo vision calls for Infinispan anyway.
However, with 4.2 - I can't make it work - my guess is the config is off some place.
Steps:
1) startserver -r websocket
2) Open
file://localhost/D:/tools/infinispan-4.2.0.FINAL/etc/sample-websocket-client.html
in Opera (with WS enabled) or Chrome
3) Put "Hello" and "World"
4) clear out "World"
5) Get "Hello"
But nothing happens, no error messages on the console nor browser for Opera
with Chrome I get keyChange is not defined and cache is not defined
Visiting
http://localhost:8181/infinispan-ws.js in Chrome does return the JS so the
server is responding."
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira