STOMP with cluster behind apache

When I run Twitalytics on a single torquebox server and connect directly, the stomplet works great and dynamically updates the list of tweets at /customers/index

However, when I start the two clustered torquebox servers and have them behind apache, the Twitalytics app works fine at http://localhost:8000 and the twitterstreamservice and deleteoldstatuses work, but the list of tweets at /customers/index does not update (if I reload the page it does load the new tweets, so I know they are being created).

Should the stomplet work in the clustered mode? Does it also have to be a singleton? Do I have to do something with port forwarding or something else to get the stomp service to work through apache?

Thanks,

Will

that’s a good question, and something I hadn’t considered. I think you may be able to comment out:

stomp do
  host 'localhost'
end

in the torquebox.rb, and it will pick up the host itself (which is really what is causing the problem I suspect).

Tried that, but it failed. I got help from the good folks at TorqueBox HQ (Thanks Ben!)

What you actually do is change ‘localhost’ to the IP you bound the torquebox servers to. In my case running on my local machine

stomp do
  host '192.168.1.8'
end

That’s unfortunate because it means each node would need a different configuration. I think that should be improved in TorqueBox.

I’ve create errata for the book to mention this issue:
http://pragprog.com/titles/jkdepj/errata#e49623

Thanks!