Hi Gordon, thanks for your answer.
On Thu, May 23, 2013 at 2:55 PM, Gordon Sim <[email protected]> wrote: > The situation with that store plugin has been a little messy. In reality > there isn't a clean interface between the broker and the store and the store > is in effect just another part of the broker codebase. In fact, as of 0.22 > the store is included in the qpid-cpp release (requires cmake to build it > however), so going forward this should be a lot easier. > > When you built from sources, did you use the full qpid sources or just the > -cpp- tarball? It looks to me like building against an installed qpid has > been broken for at least a couple of releases. Using the > --qith-qpid-checkout and --with-qpid-build may be required. (Kim, am I > missing something here?) Hm.. thats kind of what I feared. The problem is that I have a distributed setup of Qpid brokers with routes in between them and I need to make sure that routes are available after a broker restart. I see two ways to solve this: a) The broker remembers the routes after a restart. b) I need a watchdog that magically gets to know when the broker got restarted, and then adds the routes again. Since a) currently is problematic, as you pointed out, I'm kinda stuck with b). Can you think of a way some sort of watchdog thread in a process is informed that the broker died *besides* polling it constantly? I could have the watchdog process spawn qpidd, so I get SIGCHILD when the broker dies, but that doesn't seem very elegant to me. Is there a better way? Thanks in advance as usual, Christian --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
