Comment 9 for bug 1478135

adding oslo.messaging.

after more playing, i've noticed this:
if a notifier is enabled at any point in notification agent (whether it's notifier/rpc publishers or workload_partitioning), the notification agent will constantly consume cpu.

BUT
if a notifier is not enabled at any point in notification agent (udp/test publisher and no workload partitioning) all is fine.

i'm not sure why you can't have a listener and notifier in the same service without having it consume constant cpu... my only guess right now is something to do with a shared transport?