Robbie,
thanks again for your answers.
As for your first suggestion:
"connecting an ActiveMQ JMS client to the ActiveMQ
broker and a Qpid JMS client to the Qpid broker within the same JVM"
Is this going to be possible in practice? I'm something of a novice at Java
too. Will there be some kind of conflict if trying to use both the ActiveMQ
JMS client and the Qpid JMS client APIs in the same process? How would/could
this be done (example build command)? Thus far I have been building simple
example code from the command line and referencing the relevant .jar
dependency in the classpath params for both javac (build) and java
(runtime).
Finally,
today I've been looking at getting the simple Hello.java example running on
the ActiveMQ broker.
Obviously, this means I have to use a JMS AMQP 1.0 client, so I've been
using the Qpid JMS 1.0 client.
I've encountered some issues which seem to relate to the Connection URL
syntax from the JNDI (hello.properties) file.
For instance,
in a previous Qpid client talking AMQP 0-10 with a Qpid broker, I used:
amqp://username:password@clientid/test?brokerlist='tcp://localhost:5672'
however I've read and seen in practice that this won't work with the 1.0
client.
Instead I have to use something like:
amqp://username:password@localhost:5672
Can somebody please point me to the relevant documentation that explains
this difference in syntax. For all my digging on the Qpid website, I can
only find examples of the first/former (0-10 style), with no disclaimers or
caveats regarding the 1.0 client.
In addition, I've found I can use "queue://" or "topic://" prefixes in the
JNDI properties to specify the object type when using the generic interface
(i.e. general instead of p2p/pub-sub). Is that syntax a feature of the AMQP
protocol, or something specific to the Qpid client or ActiveMQ broker? I
can't find much mention of it anywhere.
Thanks again for giving these questions your attention!!
-----Original Message-----
From: Robbie Gemmell
Sent: Saturday, February 15, 2014 2:57 PM
To: [email protected]
Subject: Re: New User JMS API Questions
On 14 February 2014 04:55, Mark Barker wrote:
If anyone has a tried this, or can confirm:
will it be possible to have a JMS client using an ActiveMQ broker on one
machine (or maybe a producer/consumer pair), ultimately sending a message
which then routes to a Qpid broker and associated local JMS consumer on a
second machine (preserving all standard and application-specific JMS
message headers/properties). Has this been done and are there further
tricks, considerations and caveats here?
Maybe the ActiveMQ JMS consumer process on the first machine makes the
routing decision and then places the message via a producer instance for
the Qpid broker on the 2nd machine?
It sounds like you are talking about bridging two brokers, which you
presumably do either by connecting an ActiveMQ JMS client to the ActiveMQ
broker and a Qpid JMS client to the Qpid broker within the same JVM, or by
using the Qpid AMQP 1.0 JMS client to connect to both brokers.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
