And the troubles start:Chainsaw detects the "new" ZeroConf appender, and given the fact it's from the same station and name, Chainsaw "autoconnects" to it. But... in the Receivers tree, my app appears twice, AND the log entries appear twice, too. If I repeat the process from step 3, a new receiver is added every time, and the log entries too... really weird. Besides, some of the receivers from the tree can be "shutted down", and some others not. As result of this, my app sometimes get stuck, can't exit, and the local port binded until I manually terminate the process.Am I doing something wrong? Am I using Chainsaw in a way it is not expected?
Nope, I think that's a bug. I'll have to have a look, it's not supposed to auto-connect if there is an existing SocketHubReceiver already configured, waiting to auto-reconnect.
Re: your app getting stuck. That might be because of a non-daemon thread in the SocketAppender stuff, I will investigate that as well.
cheers, Paul
smime.p7s
Description: S/MIME cryptographic signature
