[rabbitmq-discuss] Plugin startup behavior issue

[Gavin M. Roy]

On June 17, 2014 at 1:24:14 PM, Simon MacMullen (simon at rabbitmq.com) wrote:

Probably the right solution is for the empty_db_check to only check for 
absent vhosts and exchanges. I'll file a bug for that. 
Cool, makes sense.

But how can you work around this? I don't think you can tweak the boot 
steps required by your supervisor, but I think: 

start_link() -> 
+ rabbit:maybe_insert_default_data(), 
mirrored_supervisor:start_link( 
{local, ?MODULE}, ?MODULE, 
fun rabbit_misc:execute_mnesia_transaction/1, 

is a reasonable workaround. 
Thanks! Indeed that works fine. Thank you very much for investigating.

I ran into one other issue on startup, having to do with rabbit_direct_client being available. The solution I came up with was to use timers to defer the commands until rabbit_direct_client_sup exists. Does this seem like a sane approach?

https://github.com/aweber/pgsql-listen-exchange/commit/c60d6dcc982056978750fe218e9a1ae2bf895aa3

Thanks for all your help,

Gavin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140617/f4e2b543/attachment.html>