# Node-red-contrib-msg-queue - Only storing not forwarding w/ active connection

**URL:** <https://discourse.nodered.org/t/node-red-contrib-msg-queue-only-storing-not-forwarding-w-active-connection/44274>\
**Category:** General\
**Created:** [16 April 2021 11:46 UTC](https://discourse.nodered.org/t/node-red-contrib-msg-queue-only-storing-not-forwarding-w-active-connection/44274 "2021-04-16T11:46:32Z")\
**Posts on this page:** 2\
**Page:** 2

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [22 April 2021 12:15 UTC](https://discourse.nodered.org/t/node-red-contrib-msg-queue-only-storing-not-forwarding-w-active-connection/44274/21 "2021-04-22T12:15:39Z")

</div>

> [@jakonnode](#):
>
> it could be of order of few GBs

In that case possibly an sqlite backed queue would be better so that it is not all in memory at once. The current implementation clones the complete message and puts it in the queue, which is a simple javascript array. Since you know you only need the payload and topic (possibly not even topic) someone who knows about sqlite and knows a bit of javascript should have no problem modifying the code to use a database backed queue instead.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [21 June 2021 12:15 UTC](https://discourse.nodered.org/t/node-red-contrib-msg-queue-only-storing-not-forwarding-w-active-connection/44274/22 "2021-06-21T12:15:49Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.

[Previous page](https://discourse.nodered.org/t/node-red-contrib-msg-queue-only-storing-not-forwarding-w-active-connection/44274.md?page=1)