In this case you best source of info is the code. Stepping into the FailovetTransport start method and the reconnect method may show what is going wrong. On Nov 30, 2011 12:40 PM, "JRR" <j...@cisco.com> wrote:
> Hello Tim, > > I tried the test using version */3.4.0/* of ActiveMQ-CPP and the problem > remains the same. The connection factory creates a connection even if there > is no broker running, and I've set the parameters to not try forever. Then > when start is invoked on the connection it blocks until the broker is > started. > > Moreover, as a debugging attempt, I tried without the default failover > settings (infinite waits, etc). It appears that the initial behavior for > connecting to the broker isn't working correctly, in that it does not > appear > to honor the startupMaxReconnectAttempts value. > > Or, I'm doing something wrong. > > Suggestions? > > Thanks, > > -=John > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Do-activemq-cpp-connection-questions-tp4119766p4123969.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
