qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robbie Gemmell <robbie.gemm...@gmail.com>
Subject Re: Unable to send message with Proton client
Date Fri, 18 Dec 2015 18:59:53 GMT
Hi Mark,

Proton started initially as a pure protocol engine that would be used
by other components such as brokers/clients/routers/other to support
AMQP 1.0, rather than itself being as any type of direct client etc.
That is how proton-j continues to see most of its usage that I am
familiar with, e.g within the Qpid JMS client, the ActiveMQ brokers.
It hasn't had as much work on fleshing out other areas as there has
been on proton-c and its various language bindings.

Over time and mostly on the proton-c side of things Messenger emerged
as kind of message-oriented API, and eventualy a Java port of it was
written which is what you are trying to use below. Messenger in
general isnt getting as much developer attention these days, but the
java port of Messenger in particular has never seen very much
attention since it was written originally, we likely need to have a
discussion in the community about its future (probably best reserved
for the new year when folks are actually around).

Since then, there has been more work in other areas such as the python
bindings for proton-c around creating a reactive API for client (or
other) usage, and a 'reactor' within proton-c for use by e.g those
bindings as well as those in order languages, with C++ reactive API
work ongoing now as well as bits for Go. A Java variant of the reactor
was added too, I'm not particularly familiar with it but I believe
there are some examples for it too, though I don't think its been
quite as fleshed out for simple application usage as the others have.

In terms of what you actually did below, one thing that springs to
mind is that I'm not sure 'messenger-j' ever supported anything other
than ANONYMOUS SASL. If thats still the case, the user/pass you
mention below may not even be getting used, and if the broker isnt
then offering ANONYMOUS suppport (which it doesnt by default) then
that might be a reason things aren't working at all.


On 18 December 2015 at 15:41, Mark Soderquist
<SoderquistMV@ldschurch.org> wrote:
> I am working on implementing an AMQP client with the proton-j 0.11.1 library. I found
the example Java code that comes with the project and have implemented a simple send client.
So far, however, I am unable send any messages. The code executes and exits without exceptions.
I am working with a Qpid 6.0.0 Java broker using AMQPS and have also included the bouncycastle
library in my project to support TLS. Here is the code I have implemented to see what I have
>       String uri = "amqps://" + username + ":" + password + "@" + host + ":" + port +
"/" + queue;
>       try {
>             Messenger messenger = Proton.messenger();
>             messenger.start();
>             Message message = Proton.message();
>             message.setAddress( uri );
>             message.setSubject( "test" );
>             message.setBody( new AmqpValue( payload ) );
>             messenger.put( message );
>             messenger.send();
>             messenger.stop();
>       }
>       catch( Exception exception ) {
>             exception.printStackTrace( System.err );
>       }
> Here is a sample URI with the username and password changed: amqps://username:password@qpid-test.ldschurch.org:5671/test
> ---
> Mark Soderquist
> Engineering Manager | Enterprise Integration
> The Church of Jesus Christ of Latter-Day Saints

To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org

View raw message