node-stomp-client icon indicating copy to clipboard operation
node-stomp-client copied to clipboard

Large messages break subscribe functionality.

Open JohnKossa opened this issue 8 years ago • 3 comments
trafficstars

It appears that messages above some certain size break subscription handling.

Tried a code snippet along the lines of:

socketClient.connect(function(){
    logger.info("Subscribed");
    socketClient.subscribe("/queue/connector", function(body, header){
        console.log("Something Happened!")
    });
});

When I publish messages into /queue/connector, it seems to handle messages of at least length 3509, but it breaks for messages with length 119858. I haven't zeroed in on the magic number yet.

Additionally, when it fails once at processing the large message, subsequent short messages also start failing.

I added some print statements to the library's lib/client.js frameEmitter's on 'MESSAGE', handler and those don't even get triggered when I publish a large message, so I'm guessing the problem is happening upstream from there.

JohnKossa avatar Sep 21 '17 22:09 JohnKossa

any chance you could put together a test case for this?

easternbloc avatar Nov 08 '17 12:11 easternbloc

I'll try to put something together for it this evening.

JohnKossa avatar Nov 08 '17 17:11 JohnKossa

did you ever get this solved ? I'm hitting the same thing

jmls avatar Apr 15 '18 20:04 jmls