Hi Tom, RE: It appears that qpid-config does not work for the Java broker. Is this still correct?
You may have seen some of my postings with respect to QMF and implementation of a QMF based management GUI. This was initially for the C++ broker however you might be interested to know that I'm currently working on a QMF Management Plugin for the Java Broker.
So far I've got it working for viewing statistics, but I'm planning on implementing most of add/delete stuff this weekend.
With a bit of luck I'll have something releasable by the end of the weekend if you keep an eye on the mailing list.
Initially it'll just be a new release of the qmf2 tarball attached to the QMF jira, but I need to look at getting it properly in to the main Qpid code base after that.
It's worth mentioning that the Java broker has its own management UI on host:port:8080/management you might want to try that too. I'm trying to provide a unified view across a mixed economy of C++ and Java brokers so I tend to prefer the QMF approach. My QmfManagementPlugin works with qpid-config, though you'd need to use a recent version (0.18 or 0.20) the early versions used QMF1 but my Agent only talks QMF2.
I'll keep you posted. Best regards, Frase On 07/03/13 14:26, Tom M wrote:
We are attempting to set the configuration for our qpid broker in development of a production system. It appears that qpid-config does not work for the Java broker. Is this still correct? I see that we can set the config for the exchanges and queue in the virtualhosts.xml. But, I can not find any documentation or examples about setting the binding (routingkeys) in this config file. Is it possible to config the bindings from this file? If so, can you provide the syntax? I have found that setting static bindings for static Direct Exchange to static queue does work for the Java broker (and we have had success providing messaging this way with the Java broker). We can staticly configure the bindings (as well as the exchange and queues) via the C++ client lib, using session exchangeBind( ), from a static Direct Exchange and static queue. Also, can successfully set via Jconsole. But, we don't want to have to use these methods for our production system (we are attempting to get away from the C++ client lib, and then I don't even see this available for the messaging lib.) We would prefer to set our mission operational messaging elements via a config file (or config script or Java app) on broker start up. This is primarily driven by our HA requirements. For HA, for these primary command and responses messages, we need our exchanges, queues and bindings to be static so that if any of the involved components goes down, we will not lose any messages. Also, we need to set bindings such that, in some cases, a single message into given exchange needs to route to multiple queues. And, also, some queues need to be bound to multiple exchanges. A little broader question.... If qpid-config does not work for the Java broker, is there some other a way to provide the config that will work for both the Java and C++ broker? We would like to have the flexibility to config with either. thanks, Tom Maggio
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
