Issue #9158 has been updated by Digant Kasundra.
We are running 1.1 and were hoping to not have to keep rolling our own libstomp package, but maybe an upgrade is the proper fix. Generally, we prefer to not have to roll out our own packages (since that doesn't scale well), but looks like we already did that to get us to 1.1, which we needed to make stomp work at all back in the day. If you can use introspection to call the method that is available, that would be great. If not, we'll use the patch for now and then upgrade stomp when we can. ---------------------------------------- Bug #9158: Puppet master breaks on trying to send message to stomp queue https://projects.puppetlabs.com/issues/9158 Author: Digant Kasundra Status: Needs More Information Priority: Normal Assignee: Digant Kasundra Category: queuing Target version: Affected Puppet version: 2.7.1 Keywords: Branch: When a client checks in to the puppetmaster, the puppet master attempts to send a message to the stomp queue (if async stored configs is on) and in doing so attempts to use a method that doesn't exist. This effectively completely breaks puppet in 2.7.1 for us. The following patch will fix this: --- stomp.rb.orig 2011-08-22 17:30:16.000000000 -0700 +++ stomp.rb 2011-08-22 17:13:07.000000000 -0700 @@ -29,7 +29,7 @@ end def publish_message(target, msg) - stomp_client.publish(stompify_target(target), msg, :persistent => true) + stomp_client.send(stompify_target(target), msg, :persistent => true) end def subscribe(target) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" 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-bugs?hl=en.
