Hi Cyril,
no Qpid Broker-J does not support QMF. Qpid Broker-J does support
management over AMQP using the draft AMQP Management specification, whereby
you send messages to a node "$management" to perform management
operations. Since the AMQP spec is in draft this is not yet documented as
the
Is it QMF available/compatible with Qpid Broker-J 7.0.x and Qpid JMS 0.30.0 ?
If yes, how to unable it?
Cyril
-Message d'origine-
De : Cyril Micoud
Envoyé : jeudi 15 mars 2018 10:34
À : users@qpid.apache.org
Objet : RE: Qpid JMS 0.30.0 or Qpid Proton-J 0.26.0
Hi Robbie,
Thanks for your answer, I agree with you on the "dynamicQueues/" usage...
But about the VirtualHost/Exchange/Queue management, what is the best way with
Qpid Broker-J 7.0.x? REST api or JMS message or any other solution?
Cyril
-Message d'origine-
De : Robbie Gemmell
If you are 'reloading' an InitialContext to add new JNDI config, then
depending on how you do that exactly I'd guess your application is
coupled to either the syntax of the properties it uses or maybe just
the implementation class. In either case, you could as well use
session.createQueue() etc to
We use Qpid Broker-J 7.0.x...
We have build a REST service based on Retrofit but it is very coupling with
POJO structure (we use Custom POJO instead of Map return by
REST api due to the simplicity to understand which object we manipulate).
After see management via JMS message, I
On 14 March 2018 at 17:13, Cyril Micoud wrote:
> Thanks Gordon and Robbie for your answers.
>
> I have found the vertx-proton just few second before your response... it
> is very simple and I think we are going to use it to provide a light and
> simple server on our
Thanks Gordon and Robbie for your answers.
I have found the vertx-proton just few second before your response... it is
very simple and I think we are going to use it to provide a light and simple
server on our "client" java side.
About JMS, I have seen a link (but where?) to manage
On 14/03/18 12:19, Cyril Micoud wrote:
how each system knew the dispatch router?
They just need a host and port; that would be the same even if one was
directly connecting to the other.
-
To unsubscribe, e-mail:
As Gordon noted, the JMS client can't act as a server for incoming
connections. Its only a client and must connect out, but the other
side can be a broker/router/toaster/other.
The 'reactor' impl which proton-j includes can accept, and there is a
very basic/incomplete/naive 'recv' example which
Hi Gordon,
Thanks for your answer...
We are agree with your first point and we look to try it as soon as possible.
But we have also a 3rd system in Java and we need a direct access Java=>Java
without any broker.
I think the solution is your second point?
In that case, how each system knew the
On 14/03/18 08:40, Cyril Micoud wrote:
Hi everybody,
We are working with Qpid to set up interoperability between 2 systems,
one in Java, the other in C ++.
On the C ++ side, we use Qpid Proton 0.17.0 (not the last update due to
system constraints) to use the AMQP 1.0 standard.
In Java, we
11 matches
Mail list logo