Thread handling on BusControl.Start() and .Stop()

[Kenneth Avner]

Hello,

I should be getting back to you soon on the issue I had before X-mas with state machine instances, but before I get to that; here is a question on a different matter;

In the two last versions, after implementing the support for clusters in RabbitMQ, the following can be observed upon starting MT with no MQ running (in a Topshelf host):

- I call BusControl.Start()

- MT tries to connect to RMQ, but fails

- Exception is thrown

- The Topshelf HostFactory.Run() method returns with a "AbnormalExit" code

- BUT STILL; a background thread hosting the RabbitMQ client continues to try connecting to the broker

RabbitMQ connection failed: Connect failed: user@localhost:5672/

RabbitMQ connection failed: Connect failed: user@localhost:5672/

RabbitMQ connection failed: Connect failed: user@localhost:5672/

RabbitMQ connection failed: Connect failed: user@localhost:5672/

Is this in any way by design, or should I report it as a small bug? Not a biggie, as the service process is killed after reporting false on the startup-call, but still..

-Kenneth A

[Chris Patterson]

Seems like a bug, it should stop, preventing further reconnections.

--
You received this message because you are subscribed to the Google Groups "masstransit-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to masstransit-discuss+unsub...@googlegroups.com.
To post to this group, send email to masstransit-discuss@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/masstransit-discuss/27803c1f-2e1e-4860-aee0-29e7d4f6d634%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Kenneth Avner]

Ok, tracked it (#781)