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

Trial and error to understand extra msg attributes. #3

Open
TinajaLabs opened this issue Feb 7, 2018 · 0 comments
Open

Trial and error to understand extra msg attributes. #3

TinajaLabs opened this issue Feb 7, 2018 · 0 comments

Comments

@TinajaLabs
Copy link

In the In Node I see the ability to direct a flow into a queue. However I was stumped as to where I should enter the name of the queue.

I first inserted a function node to the input side (left) of the In Node and entered this code:

msg.readFrom = "test1";
return msg;

Then I found that the adapted msg in the function node was never input into the In Node so I added an inject node in front of the function node to "Inject once" at 0.1 seconds.

This seems to have activated the In Node.

Now I can see the output of the test1 queue from the output of a debug node. -- Also, I'm still confused about why I get output from an In Node but that question is described in another issue.

Similarly I am collecting a stream of metrics on a TCP port 2007. I am directing that stream into the test1 queue with an Out Node, and I was getting an error that I was missing a value: isFullfilled.

In between the TCP Port Listener and the ampq2 Out Node I added a Function Node with the following:

msg.isFullfilled = true;
return msg;

The attribute is added to the default payload msg and the error has gone away.

I suggest adding some details about how one is expected to add these extra attributes to the ampq2 nodes.

Thank you,
Chris.

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

1 participant