Value out of range

gopinath.m · 28 February 2023 15:01

Hi I am receiving some messages from azure cloud and converting them into JSON Object .but sometimes i am getting below error,can anyone guide me how to solve this issue.
[error] RangeError: The value of "value" is out of range. It must be >= 0 and <= 255. Received -19
at new NodeError (node:internal/errors:371:5)
at writeU_Int8 (node:internal/buffer:738:11)
at Buffer.writeUInt8 (node:internal/buffer:748:10)
at BufferBuilder.appendUInt8 (C:\Users\Admin.node-red\node_modules\buffer-builder\buffer-builder.js:44:15)
at Object.encoder [as encode] (C:\Users\Admin.node-red\node_modules\amqp10\lib\types.js:390:61)
at Object.encoder [as encode] (C:\Users\Admin.node-red\node_modules\amqp10\lib\types.js:429:17)
at Codec.encode (C:\Users\Admin.node-red\node_modules\amqp10\lib\codec.js:174:20)
at Codec._encodeObject (C:\Users\Admin.node-red\node_modules\amqp10\lib\codec.js:232:48)
at Codec.encode (C:\Users\Admin.node-red\node_modules\amqp10\lib\codec.js:181:32)
at Object.listBuilder [as encode] (C:\Users\Admin.node-red\node_modules\amqp10\lib\types.js:112:43)
at Codec.encode (C:\Users\Admin.node-red\node_modules\amqp10\lib\codec.js:174:20)
at Codec._encodeObject (C:\Users\Admin.node-red\node_modules\amqp10\lib\codec.js:232:48)
at Codec.encode (C:\Users\Admin.node-red\node_modules\amqp10\lib\codec.js:181:32)
at Codec._encodeObject (C:\Users\Admin.node-red\node_modules\amqp10\lib\codec.js:219:10)
at Codec.encode (C:\Users\Admin.node-red\node_modules\amqp10\lib\codec.js:181:32)
at Object.frames.writeFrame (C:\Users\Admin.node-red\node_modules\amqp10\lib\frames.js:46:11)

gopinath.m · 1 March 2023 12:30

i have got some idea from the below link i have stringified (Serialized) the incoming message and then parsed (deserialized) it again ,looks that had solved a problem for somebody .i am going to try this.

github.com/amqp/rhea

RangeError [ERR_OUT_OF_RANGE] after longer operation times

opened 01:52PM - 07 Dec 18 UTC

closed 02:17PM - 14 Dec 18 UTC

sh-developers

### Background We implement request/response communication pattern via AMQP and… use Qpid (C++ version) as the amqp broker. We ported our applications from amqp10 to rhea because when we moved from node 8 to node 10, we started getting buffer write errors (very similar to the one I'm about to show you). We create our receiver queues via the same connection using the QMF2 framework (which is probably not relevant, because the error only occurs on sender connections, for which the queue is created by other services). ### Description The errors we have encountered with rhea only start showing up after the application has run for a while (in this case a day on a low traffic test server). These errors start with the number 256 and start counting up from there (281 in the example). We have only observed this error occurring when we are *sending* to an already existing queue. ### Example ``` [RangeError [ERR_OUT_OF_RANGE]] "The value of "value" is out of range. It must be >= 0 and <= 255. Received 281" RangeError [ERR_OUT_OF_RANGE]: The value of "value" is out of range. It must be >= 0 and <= 255. Received 281 at writeU_Int8 (internal/buffer.js:559:11) at Buffer.writeUInt8 (internal/buffer.js:569:10) at types.Writer.write_uint (/app/node_modules/rhea/lib/types.js:725:28) at types.Writer.write_variable_width (/app/node_modules/rhea/lib/types.js:751:10) at types.Writer.write_value (/app/node_modules/rhea/lib/types.js:789:14) at types.Writer.write (/app/node_modules/rhea/lib/types.js:779:14) at types.Writer.write_compound (/app/node_modules/rhea/lib/types.js:814:18) at types.Writer.write_value (/app/node_modules/rhea/lib/types.js:791:14) at types.Writer.write (/app/node_modules/rhea/lib/types.js:779:14) at types.Writer.write_compound (/app/node_modules/rhea/lib/types.js:814:18) ``` ### Further observations Because the number always counts up, we think that the number being written might be a counter of some sorts? We use a correlationId consisting of a string (ULID-identifier), so it cant be that. All other information being non-counting, the only other number we send ourselves is the userId number, which is always the same on this environment, and is always observed to be in the tens not in the hunderds (and counting up). If you need any further information, please tell us.

system · 30 April 2023 12:31

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

Topic		Replies	Views
Problema con un flow General	26	975	15 May 2022
Function node error checking General	7	1125	14 September 2019
Schneider modbus Float32 IEM3350 Industrial	3	907	5 November 2020
Unopened section "payload" at 4893 General	21	603	8 October 2021
If not equal to "string" and equal to number - function node General	4	311	23 January 2023

Value out of range

Related Topics