Routing messages between two brokers

[Steve Huston]

I am bootstrapping my dispatch router knowledge on a little project driven by 
the need to feed messages through:

- AMQP 0-10 client sends messages to a broker that speaks both 0-10 and 1.0
- dispatch router takes messages out of that dual-protocol broker and routes 
them to another broker that speaks only 1.0

... and back the other way, with a different named queue.

So here is the qdrouterd.conf pieces for this goal:

router {
mode: standalone
id: Router.A
}

#Listener for the dispatch-router management connections - qdstat
listener {
host: 0.0.0.0
port: amqp
authenticatePeer: no
}

connector {
name: otherbroker
host: otherhost
port: 5672
role: route-container
}

connector {
name: appbroker
host: 0.0.0.0
port: 10053
role: route-container
}

address {
prefix: to.myapp
waypoint: yes
}

autoLink {
addr: to.myapp
connection: appbroker
dir: in
}
autoLink {
addr: to.myapp
connection: otherbroker
dir: out
}

address {
prefix: from.myapp
waypoint: yes
}

autoLink {
addr: from.myapp
connection: appbroker
dir: out
}
autoLink {
addr: from.myapp
connection: otherbroker
dir: in
}


When qdrouterd runs, it appears to set up the connections and links, but no 
messages are retrieved from 'appbroker' 'to.myapp' - and there are many 
messages sitting in that queue waiting.

Is there something I'm missing to actually get the messages to flow?

Thanks,
-Steve

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

Re: [Java Broker] Usage of any certificate from keystore

[Rob Godfrey]

On 26 October 2017 at 13:27, Vavricka  wrote:

> Hi,
>
> I have working amqps in Java broker. Clients can connect without any
> issues.
>
> You can specify certificate alias, if there are multiple certificates in
> keystore. I wonder if there is possibility to use any of certificates from
> keystore. I tried '*' as certificate alias, but alias from keystore is
> expected.
>
>
I'm not sure I really understand the requirement here... it seems odd to
say "pick a random certificate from this keystore"... Something like "pick
a *valid* certificate from this keystore with the furthest away expiration
date" might make more sense I think (otherwise you'd still need to remember
to delete the expired certificate some time).  Ultimately we might also
want to introduce something to choose which certificate is served up
depending on the SNI in the client request, but that's probably a separate
piece of work.

-- Rob

Usage of any certificate from keystore can be helpful in situations when
> certificate is expiring and it needs to be replaced by newer certificate
> (certificates can overlap).
>
> Vavricka
>
>
>
> --
> Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-
> f2158936.html
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

Re: Ruby Qpid Proton Gem release

[Gregor Berginc]

Thanks Irina for sharing. Thanks Alan and the rest of the Qpid team for
making this release!

I've tested the gem from RubyGems and it works.

cheers,
-Gregor

On 25 October 2017 at 22:57, Irina Boverman  wrote:

>  
> https://rubygems.org/gems/qpid_proton/versions/0.18.0
> 
>
> On Thu, Oct 12, 2017 at 12:07 PM, Alan Conway  wrote:
>
> > Ruby is done, we are closing the final C/C++ issues today I hope, so
> should
> > be very soon now.
> >
> > On Wed, Oct 11, 2017 at 4:16 AM, sergio  wrote:
> >
> > > Any update on this. We are already in Mid-October.
> > >
> > >
> > >
> > > --
> > > Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-
> > > f2158936.html
> > >
> > > -
> > > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> > > For additional commands, e-mail: users-h...@qpid.apache.org
> > >
> > >
> >
>