[rabbitmq-discuss] Using Toke
matthew at rabbitmq.com
Mon Oct 4 18:27:30 BST 2010
On Mon, Oct 04, 2010 at 12:04:23PM -0500, tsuraan wrote:
> Is there a setup guide somewhere for the Toke plugin? The plugins
> page (http://www.rabbitmq.com/plugins.html) doesn't mention it, and
> there isn't a README in the rabbitmq-toke project. My rabbit build
> environment is just a download of the 2.1.0 tarball; I have tokyo
> cabinet installed, so after that, what do I need to do to get Toke
> running? Also, is there a way to tell that toke is running on a given
> rabbit process?
Sadly, it's all a bit of a mess just at the moment.
rabbitmq-toke requires toke, which requires tokyocabinet to be
Because we don't ship native code, and because we certainly don't want
to ship tokyocabinet, the rabbitmq-toke package was never added to our
overall list of plugins in the rabbitmq-public-umbrella repo. As a
result of this, recent changes to the public umbrella build mechanism
managed to break rabbitmq-toke (amongst other things).
I've spent the last two weeks rewriting the whole build system, pretty
much from scratch, and it's now vastly improved and rabbitmq-toke works
again now, however, that work has not yet been through QA, and is thus
only available on branch bug23274. Thus, the following should work:
First, install tokyocabinet locally, including development headers -
compiling from source is your best bet.
hg clone http://hg.rabbitmq.com/rabbitmq-public-umbrella -r bug23274
You should then see as part of the rabbit boot steps:
starting Tokyo Cabinet for rabbit_msg_store ...done
If you exit the broker, then ls dist/*.ez, you should see something
rabbitmq-toke$ ls dist/*.ez
Copy all but the rabbit_common to your server plugins dir. Now I _think_
you should be ok running these with a 2.1.0 broker, but you may not be -
you may have to run the latest broker from default.
Hopefully, this building mess will be sorted in the next day or two, as
this new work gets through QA. However, there is a general issue with
toke that we don't want to ship native code, but can't build or package
toke without. Certainly, the website plugins page should be properly
More information about the rabbitmq-discuss