Jira (MCO-177) mcollective client not working in threaded mode

[Richard Clamp (JIRA)]

Title: Message Title

Richard Clamp commented on an issue   Re: mcollective client not working in threaded mode I'm not seeing the exception in that log, but I am seeing a lot of discarded messages as one thread is discarding the responses intended for the other threads, as the client code isn't thread-safe in this manner. A possible fix for this would involve making the client incorporate the thread-id into it's reply-to address and then being more judicious in which subscriptions it will take messages from in each thread. This would probably require significant rewrite of the client code. Updating affects-versions as this affects every version of MCollective. Add Comment   MCollective / MCO-177 mcollective client not working in threaded mode Ubuntu: 13.10 ruby: 1.8.7 I`m attached a script that can reproduce the problem. In my configuration I`m using activemq as midleware. When client trying to work with multiple collectives in threads, client not able to understand who is who and falls with exception. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.