Upgrade (Work in Progress)

Auto Reconnect

Please note:

After each connect (i.e., initial connect as well each reconnection) the connectCallback will be called.
After reconnecting, it will not automatically subscribe to queues that were subscribed. So, if all subscriptions are part of the connectCallback (which it would in most of the cases), you will not need to do any additional handling.

Stomp.client, Stomp.overTCP, or, Stomp.overWS

Just add client.reconnect_delay = 5000;. The delay is in milli seconds. A value of 0 indicates auto reconnect is disabled.

    var url = "ws://localhost:61614/stomp";
    var client = Stomp.client(url);

    // Add the following if you need automatic reconnect (delay is in milli seconds)
    client.reconnect_delay = 5000;

See also:

Auto Reconnect

Stomp.over

If you were using Stomp.over like:

    <script src="http://cdn.sockjs.org/sockjs-0.3.min.js"></script>
    <script>
        // use SockJS implementation instead of the browser's native implementation
        var ws = new SockJS(url);
        var client = Stomp.over(ws);
        // ...
    </script>

Change it to:

    <script src="http://cdn.sockjs.org/sockjs-0.3.min.js"></script>
    <script>
        // use SockJS implementation instead of the browser's native implementation
        var client = Stomp.over(function(){
                                   return new SockJS(url);
                                });

        // Add the following if you need automatic reconnect (delay is in milli seconds)
        client.reconnect_delay = 5000;
        // ...
    </script>

See also:

Stomp.over

NodeJS - Stomp.overWS -> Stomp.client

Just change the method name:

    var client = Stomp.overWS("ws://localhost:61614/stomp");

    var client = Stomp.client("ws://localhost:61614/stomp");

Please note that even though both methods seem similar, these are very differently implemented.

See also:

NodeJS - Stomp.overTCP -> Stomp.client

See also:

It is little more involved than it seems. The following is a summary:

Ensure that your STOMP broker is configured to communicate STOMP over WebSocket.
Get the WebSocket endpoint URL - typically like ws://localhost:61614/stomp

    var client = Stomp.overTCP("localhost", 61613);

    var client = Stomp.client("ws://localhost:61614/stomp");

Do test your application.

SockJS -> WebSocket

Summary of steps:

Ensure that your STOMP broker is configured to communicate STOMP over WebSocket.
SockJS and WebSocket use different handshake mechanism, so, their end points are likely to be different.
Get the WebSocket endpoint URL - typically like ws://localhost:61614/stomp
Replace your code to create Client similar to:

    var client = Stomp.client("ws://localhost:61614/stomp");

See also: