You’re about to write a bug :-P There should be no minimum and maximum time… in recovery, it could take 5-15 minutes.
Just write a waitForPort() look and try to connect the port on startup and put some reasonable bound in there. Say 5 minutes. I usually don’t use connectTimeout though because that shouldn’t block forever. Also, just keep ActiveMQ running all the time as a daemon. On Wed, Feb 4, 2015 at 7:53 PM, Ramesh Rocky <[email protected]> wrote: > Hi, > I start the activemq and immediately start the flume using process flume > throws an execption "javax.jms.JMSException: Connection reset" because > activemq take some time to start completely. After some time start flume > it does n't throws exception. > Here I want to know the what is the minimum and maximum time require to > start the activemq completely. > > Thanks & RegardsRamesh -- Founder/CEO Spinn3r.com Location: *San Francisco, CA* blog: http://burtonator.wordpress.com … or check out my Google+ profile <https://plus.google.com/102718274791889610666/posts> <http://spinn3r.com>
