Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TypeError: Cannot assign to read only property 'writeQueueSize' of object '#<TCP>' #21

Open
GTerryLiu opened this issue Oct 21, 2019 · 3 comments

Comments

@GTerryLiu
Copy link

I used amqp sender to send messages to rabbitmq. And I found that rabbitmq received the message. But on node-red console, the server stopped by errors. The error message is as below.
TypeError: Cannot assign to read only property 'writeQueueSize' of object '#<TCP>'
at _clone (/srv/node-red/node_modules/clone/clone.js:162:16)
at _clone (/srv/node-red/node_modules/clone/clone.js:162:18)
at _clone (/srv/node-red/node_modules/clone/clone.js:162:18)
......

Node.js version: v10.16.3
Node-RED version: v1.0.2

Can somebody help?

@GTerryLiu GTerryLiu changed the title TypeError: Cannot assign to read only property 'writeQueueSize' of object '#&lt;TCP&gt;' TypeError: Cannot assign to read only property 'writeQueueSize' of object '<TCP>' Oct 21, 2019
@GTerryLiu GTerryLiu changed the title TypeError: Cannot assign to read only property 'writeQueueSize' of object '<TCP>' TypeError: Cannot assign to read only property 'writeQueueSize' of object '#<TCP>' Oct 21, 2019
@pratham2003
Copy link

pratham2003 commented Apr 27, 2020

I'm getting a similar error too when using node-red chatbot.
But the error is probably related to redUtil.cloneMessage ?

@roxannems
Copy link

Hi there! I've run into the same error on Node-RED version 1.0.2. I haven't found a solution for this on that version, however, upgrading node-red to v1.1.2 fixed it for me. Hope it helps.

@GTerryLiu
Copy link
Author

GTerryLiu commented Apr 13, 2021

Hi there! I've run into the same error on Node-RED version 1.0.2. I haven't found a solution for this on that version, however, upgrading node-red to v1.1.2 fixed it for me. Hope it helps.

Thanks. I just changed codes on v1.0.2 and the error disappeared. What I changed is adding a line as following.

add "delete msg.delivery.link" before line 282 in rhea.js

I know that it was just a solution temporarily. I think you just bring a regular solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants