Fix/751 rpc with different routing keys

[vhforbes]

Hey there,

Regarding the issue: #751

I'm not experienced enough to really find the core problem so that the @RabbitRPC only listen to messages with the correct routingKeys.

Anyhow, I've wanted to propose a change so that if the routingKey is invalid, the message to be requeued so it can be picked up by the correct listener.

Any suggestions on how I can solve this in a better way are welcomed. I would do this fix only In my own code but realized it might be useful for someone else.

Thanks a lot for the lib!

[underfisk]

Thank you @vhforbes for the contribution. In order to us to accept such behavioural change, we would need a test coverage update and possibly one more person's feedback since this will switch the behaviour.

[vhforbes]

Hey @underfisk , what do mean by a test coverage update? As I can see right now there are no existing tests for the setupRpcChannel. I don't know how I can provide someone else feedback other than what's already in the issue #751, should I ask there if the change makes sense?

[vhforbes]

I've just reread some RMQ docs and believe it its the intended behavior to have separate queues for different processes instead of splitting them using only routing keys. I'll close my PR since it was a misassumption but will be tuned in to improve the lib as I can!

Thanks a lot :)