Oh ok. I have the below timeout tunable limits on my both client and server cfg files and am using stom 1.3.2.
plugin.activemq.heartbeat_interval = 30 plugin.activemq.timeout = 5 plugin.activemq.max_hbread_fails = 2 plugin.activemq.max_hbrlck_fails = 0 plugin.activemq.stomp_1_0_fallback = 0 So should I include the tuning parameters which you suggested along with what I have? On Monday, March 20, 2017 at 12:13:12 PM UTC+5:30, R.I.Pienaar wrote: > > this is probably controlled by these: > > plugin.activemq.initial_reconnect_delay = 0.01 > plugin.activemq.max_reconnect_delay = 30.0 > plugin.activemq.use_exponential_back_off = true > plugin.activemq.back_off_multiplier = 2 > plugin.activemq.max_reconnect_attempts = 0 > > 0 on the last means retry forever > > On Mon, Mar 20, 2017, at 06:12, [email protected] <javascript:> wrote: > > Hi, > > > > Yesterday I faced an issues. My ActiveMQ middleware went down and the > mco > > command triggered with timeout value 10. But there is onconnect fail > > error > > on mco client log due to middleware down and mco command was keep > > connecting until I press CTRL+C. Is there any to run the mco command > with > > some timeout value and if its unable to connect middileware within the > > time > > period then it has to come with saying no response? > > > > > > Regards > > Ravi > > > > -- > > > > --- > > You received this message because you are subscribed to the Google > Groups > > "mcollective-users" group. > > To unsubscribe from this group and stop receiving emails from it, send > an > > email to [email protected] <javascript:>. > > For more options, visit https://groups.google.com/d/optout. > > > -- > R.I.Pienaar / www.devco.net / @ripienaar > -- --- You received this message because you are subscribed to the Google Groups "mcollective-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
