activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Basmajian, Raffi" <>
Subject RE: Transports available for networkConnectors
Date Mon, 05 Oct 2015 15:55:58 GMT
Good question, but I think a more important one to ask is: why would broker-to-broker connections
need anything other than tcp? If I configure transport connectors for stomp, amqp, etc., it's
because I'm bridging a gap between clients who speak those protocols, and the broker itself.
Brokers configured in NoB, on the other hand, talk the same language, so there's no technical
gap to bridge and thus no need to transform from one message format to another.

Is that a correct assessment or am I missing something?


-----Original Message-----
From: Christopher Shannon [] 
Sent: Monday, October 05, 2015 10:12 AM
Subject: Re: Transports available for networkConnectors [ EXTERNAL ]
Importance: High

The auto transport should work but only if the activemq-broker jar is on the classpath.  It
would just use OpenWire.

On Mon, Oct 5, 2015 at 9:50 AM, <> wrote:

> Ill keep you posted as to how the duplex works with ssl...
> Regards,
> Barry
> -----Original Message-----
> From: [] On Behalf Of Tim 
> Bain
> Sent: Monday, October 05, 2015 9:45 AM
> To: ActiveMQ Users
> Subject: Transports available for networkConnectors
> Can someone provide a list of which transports are allowed in 
> broker-to-broker networkConnectors and which are not?
> Obviously tcp works.  Barry Barnett's recent thread made it clear that 
> ssl works (though maybe not for duplex connections), which was news to me.
> says that http and 
> multicast both work, and that "ActiveMQ also supports other transports 
> than tcp", which isn't very useful.  Previous posts to this mailing 
> list made it clear that stomp doesn't work.  What's missing (other than the "wrapper"
> transports such as static, failover, etc.), and are they supported?  
> Does the new auto transport ( work there?
> I can update the documentation to capture this information if someone 
> can provide it.
> Tim

This e-mail transmission may contain information that is proprietary, privileged and/or confidential
and is intended exclusively for the person(s) to whom it is addressed. Any use, copying, retention
or disclosure by any person other than the intended recipient or the intended recipient's
designees is strictly prohibited. If you are not the intended recipient or their designee,
please notify the sender immediately by return e-mail and delete all copies. OppenheimerFunds
may, at its sole discretion, monitor, review, retain and/or disclose the content of all email
View raw message