The boot file generated as part of the plugin activation will not work across an Erlang upgrade. This is an unfortunate side-effect of the way that the Erlang release management system works. As Matthew says, simply re-running the plugin activation script should more than likely correct the problem.<br>
<br><div class="gmail_quote">On Mon, Mar 8, 2010 at 4:52 PM, Matthew Sackman <span dir="ltr"><<a href="mailto:matthew@lshift.net">matthew@lshift.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi J�r�my,<br>
<div class="im"><br>
On Mon, Mar 08, 2010 at 05:48:50PM +0100, J�r�my Lal wrote:<br>
> - upgrade erlang at some point<br>
> - restart : crash<br>
<br>
</div>Do you happen to have the error message and logs that you get at this<br>
point? I'm curious to know what has changed to the point where you have<br>
to recompile the stomp plugin. Does just running activate-plugins again<br>
not solve the issue?<br>
<br>
Matthew<br>
<br>
_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
</blockquote></div><br>