<div>
                    I'll take a look at that soon. As a work-around you can register with the callback manager to be notified when the connection closes and handle it yourself.
                </div><div><br></div><div>Check out the connection.Connection class to see how to do that.</div><div><br></div><div>Gavin</div>
                 
                  
                <p style="color: #a0a0a0;">On Tuesday, July 26, 2011 at 5:06 PM, Alex Grönholm wrote:</p><blockquote type="cite"><div>
                    <span><div><div>
    
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
    
    
    26.07.2011 19:13, Gavin M. Roy kirjoitti:
    <blockquote type="cite"><div>
      <div> <br>
      </div>
      <p style="color: #a0a0a0;">On Tuesday, July 26, 2011 at 11:57 AM,
        Marek Majkowski wrote:</p><blockquote type="cite"><div>
        <span>
          <div>
            <div>On Tue, Jul 26, 2011 at 16:08, Gavin M. Roy &lt;<a moz-do-not-send="true" href="mailto:gmr@myyearbook.com">gmr@myyearbook.com</a>&gt;
              wrote:<br><blockquote type="cite"><div>
                <div>The SimpleReconnectionStrategy implementation was
                  to on disconnect, have a<br>
                  incrementally delayed attempt to reconnect to the
                  broker. I believe there's<br>
                  a ticket with this being broken in 0.9.5, I need to
                  confirm that's the case.<br>
                </div>
              </div></blockquote><br>
              Stupid question: what happens after reconnection succeeds,
              is<br>
              the user informed in any way? What happens to things<br>
              waiting on basic_consume and such?<br>
            </div>
          </div>
        </span></div></blockquote><div>There is a callback mechanism in place the user can subscribe
        to, but it must be treated as a new connection, there is nothing
        automated but the reconnection. </div>
      <div><br>
      </div>
      <div>No channels recreated, etc. The behavior of it should mirror
        the 0.5.2 behavior as of right now. &nbsp;Future direction hasn't
        been contemplated.</div>
    </div></blockquote>
    I just need reconnection to work, but as of 0.9.5 it doesn't. Would
    be nice if it did. The callbacks will handle channel creation etc.<br>
    

</div><div>_______________________________________________<br>rabbitmq-discuss mailing list<br><a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br><a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br></div></div></span>
                  
                  
                  
                  
                </div></blockquote><div>
                    <br>
                </div>