yea, me neither. one option may be to increment the number of tries that it does. I added that test to validate there are no deadlocks in the discovery reconnect logic and made some relevant changes to improve the situatuion but there may be some gremlin still in there. In other words, the failure may be real.
2009/9/17 Rob Davies <rajdav...@gmail.com> > me neither - though I noticed Hudson was bounced - so might be an > environment thing > > On 17 Sep 2009, at 08:53, Dejan Bosanac wrote: > > Cannot reproduce DiscoveryNetworkReconnectTest failure. Anyone else tried >> it? >> >> Cheers >> -- >> Dejan Bosanac >> >> Open Source Integration - http://fusesource.com/ >> ActiveMQ in Action - http://www.manning.com/snyder/ >> Blog - http://www.nighttale.net >> >> >> On Wed, Sep 16, 2009 at 6:32 PM, Apache Hudson Server < >> hud...@hudson.zones.apache.org> wrote: >> >> See >>> >>> http://hudson.zones.apache.org/hudson/job/ActiveMQ/org.apache.activemq$activemq-core/123/ >>> >>> >>> >>> > Rob Davies > http://twitter.com/rajdavies > I work here: http://fusesource.com > My Blog: http://rajdavies.blogspot.com/ > I'm writing this: http://www.manning.com/snyder/ > > > > > > -- http://blog.garytully.com Open Source Integration http://fusesource.com
