Published Events are consumed when not subscribed to

[datalasatfotech]

I might be missing the point (entirely)

But I have two sample "apps" both connected to the same RabbitMQ queue and both using the same .proto definition, loosely following the examples given (and the tests)

I've called them "client" and "server", although the terms are meaningless I'll use those words to mark the distinction)

On the "server" I have a very simple timed function that calls "publishEvent" once a second, with a message (Simple.Event) containing a counter, when running on it's own, the "server" will log "incoming message: ..." with the inbound message. Note that it does not subscribe to anything

On the "client" I have a single call to "subscribeEvent" listening for 'Simple.Event' and doing nothing else.

Whilst they are both running, the "Client" will only see every other message, with the server logging "incoming message:" for the other message, i.e. in practice "server" logs odd numbers and client logs even ones.

Is this expected? It's certainly not what I want to do, which is to have the "server" publish events which the "client" then picks up (all of them) and will eventually issue a totally different set of messages that I'd like the server to pick up.