Recursive process.nextTick detected warning about stompit HOT 8 CLOSED

This issue has been reported before (issue #15) and a workaround was released in stompit v0.21.

The warning is caused by a flaw in node's stream implementation. This type of detection and warning was removed from node in v0.11.10.

If you're unable to upgrade node then you can suppress the warning by increasing the value of process.maxTickDepth variable.

from stompit.

Thanks for the fast reply. We are stuck on 0.10 for now so I'll use the
work around. Does this affect 0.12 or io.js?
On 25 Aug 2015 8:10 am, "Graham Daws" [email protected] wrote:

This issue has been reported before (issue #15
#15) and a workaround was
released in stompit v0.21.

The warning is caused by a flaw in node's stream implementation. This type
of detection and warning was removed from node in v0.11.10.

If you're unable to upgrade node then you can suppress the warning by
increasing the value of process.maxTickDepth variable.

—
Reply to this email directly or view it on GitHub
#29 (comment).

from stompit.

Neither are affected. From 0.11.10 onwards, node and io.js allow nextTick infinite recursion. The test I used to reproduce the problem worked without issue in v0.12 and io.js v1.

from stompit.

Thanks :)

from stompit.

Does this mean while a message is in transit (between client and server), process.nextTick loop will block any other operations on the node server (e.g. express won't process other connection requests)??

from stompit.

No, the node server won't be blocked by stompit reading a message.

A limited amount of nextTick recursion occurs in stompit when for example a large chunk of data, containing possibly hundreds of messages, is read on the socket. All the messages can be read and processed immediately in a nextTick loop if there's no external I/O requested or pauses in between by the subscriber. If enough messages are processed at once it triggers the nextTick recursion warning. No blocking occurs, the nextTick loop exits and control returns to the event loop when there's nothing left to read or when reading pauses on the socket. There's no blocking during reading.

from stompit.

Thanks for the into

from stompit.

*info

from stompit.