TypeError: Cannot read property 'publish' of undefined about stompjs HOT 9 CLOSED

There is a delay between calling client.activate and the actual connection getting established. You have two options:

• Write your code inside onConnect. However, onConnect gets called every time a connection is established (like a reconnect after an error).
• Check for Client#connected before calling publish.

There is wrapper of this library - https://github.com/stomp-js/rx-stomp - that uses rxjs. That wrapper supports local queuing of messages if the underlying connection is not there.

from stompjs.

Cool, onConnect is working but while publishing, how do I check what message I'm publishing? using debug I get only ping pong but not the actual message that I'm publishing.
I want to log the message, where is it available?

onConnect: function(frame) { client.publish({ destination: "/topic/t1", body: "Bla Bla" }); console.log("Client connected to", frame.headers.server); console.log(client); },
I just get the content-length as 7 using debut, but not the actual message from subscriber.

from stompjs.

Please try setting https://stomp-js.github.io/api-docs/latest/classes/Client.html#logRawCommunication

from stompjs.

This can be set using config as well.

from stompjs.

Thanks for your help. Why is there no disconnected method? I wanted to configure to handle activemq failover after every thing is set up and started and stopping message delivery in case of activemq failover.
maybe something like:
if(client.disconnected) client.reconnect()
so that the publisher doesn't post if my active mq stops responding.

#client.active is something I found but it is not serving my purpose.

from stompjs.

reconnectDelay: 5000 in the configuration will trigger automatic reconnect in 5000ms. Please see https://stomp-js.github.io/guide/stompjs/2018/06/28/using-stompjs-v5.html#lifecycle-callbacks for different callbacks. In general this article is a good read.

from stompjs.

reconnectDelay only works if my activemq is not running and I start my producer, it'll tell me it's trying to reconnect. But let's assume a scenario where my activemq is running and my producer is also running and suddenly activemq is stopped. Now the problem is it's trying to reconnect but at the same time it's also publishing to the queue as well.
I need to handle the fail over in a way that once the activemq is disconnected even though publisher is publishing, it should stop publishing and try to reconnect only.

from stompjs.

When the broker disconnects for any reason, https://stomp-js.github.io/api-docs/latest/classes/Client.html#onWebSocketClose will be called and https://stomp-js.github.io/api-docs/latest/classes/Client.html#connected will be set to false.

Depending on your application needs I can suggest one of the following:

• You can listen for https://stomp-js.github.io/api-docs/latest/classes/Client.html#onWebSocketClose and pause/stop publishing. Listen for https://stomp-js.github.io/api-docs/latest/classes/Client.html#onConnect and resume/start publishing.
• Before attempting to publish check for https://stomp-js.github.io/api-docs/latest/classes/Client.html#connected and publish only if it is true.

from stompjs.

Thanks for the replies, for now I've switched to node-stomp and it's working fine for my usage. For my application requirement, stomp-js is not serving my purpose!

from stompjs.