Contention between Signal and MethodReply Messages

[bcwaldon]

The inWorker event loop [0] handles both Signal and MethodReply Messages. When handling a Signal, an attempt is made to send an object over a user-provided channel. Obviously if this channel is not ready to receive, the inWorker loop will be blocked from processing any more messages. This causes major problems when Methods are called by the user in response to receipt of a Signal object.

This has been addressed in go-systemd by using two independent dbus.Conn objects (and therefore independent inWorker event loops) [1].

[0]

dbus/conn.go

Line 239 in 8d5cd58

func (conn *Conn) inWorker() {

[1] coreos/go-systemd#64

[krnowak]

I'm working on it.