No, we switched to a seperate websockets server that listens to the
active mq. But if anyone ever finds out, I'll be happy to hear a solution.
Am 15.12.2011 11:36, schrieb jmls [via ActiveMQ]:
> did you ever get it working ? We've hit exactly the same problem
>
> -
I hate replying to myself, but no one got an idea? Has anyone managed to get
the WebSockets TransportConnector to work with 5.6 or 5.5 at all?
I even replaced the Jetty libs with a newer version. I also noticed that on
telnet I get a connection to the websocket port but nothing happens when I
try t
Hey all,
today I started trying out the websockets transport connector for our amq. I
first tried the 5.5.0 version, which gave me some null pointers when I
wanted to connect. I then learned that it may not understand the newest
websocket protocols, so i changed to the 5.6.-SNAPSHOT and the errors
