----- Original Message ----- > Hi everyone, > > thank R.I.P. for the pointers. I already planed to add more > monitoring to ActiveMQ, so I'll take this as a chance. I > dont think Amazon network settings are the root cause in my case, as > I have registration agent enabled on all machines. > This should keep the connection busy. > > I filed a bug regarding the exit-code. Is there any chance the fix > will make it in 1.2.2?
No, behavior changes can't go into the current prod branch so will go into 1.3.x which should become 2.0.0 very soon - like in January maybe -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
