iOS Support about stomp-websocket HOT 8 CLOSED

I configured and ran the browsertests page too just now and Safari on the iPad passed 24 out of 24 tests. Even Chrome on the desktop didn't do that well.

from stomp-websocket.

you are browsing on the iPad and connecting to ActiveMQ on localhost? I don't understand...

from stomp-websocket.

Sorry, I changed the real IP address to localhost in the example I posted above. They're on the same network and it really said "Whoops! Lost connection to ws://10.10.1.10:61614/stomp".

from stomp-websocket.

I have seen the "Whoops!" in a few situations. One was fixed in AMQ 5.7 and it was related to using "localhost" so that should not be it. What are your message sizes? If they are large you may want to increase the max size.

Below is an example AMQ configuration:

from stomp-websocket.

Can you try posting that configuration again? The messages are maybe 1000 characters or less. It will disconnect though even if no incoming messages have been received.

from stomp-websocket.

transportConnector name="websocket" uri="ws://0.0.0.0:61614?websocket.maxTextMessageSize=999999&websocket.maxIdleTime=60000&websocket.bufferSize=32536"

It filtered the XML so I just removed the angle brackets and it went through.

from stomp-websocket.

I tried that configuration on both 5.7 and 5.8 and got the same results. Still works fine in Chrome on the desktop.

from stomp-websocket.

I checked and the chat example is working fine on my iPhone and iPad both with the latest iOS release (6.1.3 (10B329).
On the server-side, I used the ActiveMQ Apollo 1.5 broker.

I'll close this issue as it's not in the JavaScript client side and let you open one in ActiveMQ issue tracker

from stomp-websocket.