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?