Fixed rabbitmq plugin delay strategy by applying correct header

[31vi5]

The delay strategy creates a header array of application_headers which contained the x-delay instead of having the x-delay header directly. Screenshot of the message in the queue https://i.imgur.com/Qk4jyc4.png

The result was that the message was not correctly delayed. I've added the correct header to the message and then the delay started working. I've left the original property unchanged other than removing unnecessary type casting.

[makasim]

There are functional tests that cover the use of the plugin (1, 2, 3). They pass.

The issue should be investigated future. Maybe the tests are wrong, or your change is not relevant.

[31vi5]

Perhaps it might have been my misunderstanding of the feature. If I understand it correctly (which now differs from my understanding of the behavior at the time of posting the pull request), the message is sent to queue and then processed right away and then requeued with the delay, is that correct?

[makasim]

It depends on a lot of factors. Let me know what you are doing and what you use and what are the versions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.