<div>
<div><span><p style="color: rgb(160, 160, 160); ">On Tuesday, May 3, 2011 at 9:20 AM, Simon MacMullen wrote:</p><blockquote type="cite" style="border-left-style: solid; border-left-color: rgb(204, 204, 204); border-top-width: 1px; border-right-width: 1px; border-bottom-width: 1px; border-left-width: 1px; margin-left: 0px; padding-left: 10px; padding-right: 0px; margin-right: 0px; "><span><div><div>On 03/05/11 11:02, Simon MacMullen wrote:<br><br>Hmm, this works for me.<br><br>Cheers, Simon<br></div></div></span></blockquote><div><span><div><div><br></div></div></span></div></span></div><div>
<span>Hey, I've attached another plugin and startup logs for three of the nodes in the cluster to prove my alleged sanity ;-)</span></div><div><span><br></span></div><div>In reviewing the logs I did notice something interesting... In the nodes that I added to the cluster, when I had issues start_app after adding them, the "starting STOMP Adapter (binding to [61613]) ...done" line did not show. All brokers are listening on the port. The startup logs for these two nodes include the initial startup then the startup after the following commands were issued:</div><div><br></div><div>stop_app</div><div>reset</div><div>cluster [nodes to cluster with]</div><div>start_app</div><div><br></div><div>I wonder if the oddity is in that. I did not restart the brokers themselves after adding them to the cluster. They were added in order.</div><div><br></div><div>Hope this helps,</div><div><br></div><div>Gavin</div><div>
<span></span>
<!-- <p style="color: #a0a0a0;">On Tuesday, May 3, 2011 at 9:20 AM, Simon MacMullen wrote:</p> -->
<p style="color: #a0a0a0;"><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" color="#A0A0A0"><br></font></font></p>
</div>
</div>