You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Eibwen <gw...@sedonatek.com> on 2010/03/19 19:53:51 UTC
transportConnectors produce into http consume from tcp
The main producer for my setup needs to get though a firewall, its a Java
application that i do not control. So they are trying to use HTTP.
I am setting up the MessageQueue and the consumers.
The software that the consumers are interacting with are in C# so i am
trying to use NMS (which currently does not support HTTP transport)
So i am wondering how can i setup the broker to allow both types of
transports, or would i need two brokers running with a networkConnector
between them?
I will never need to send a message up to the producer, but consumers might
send messages between each other.
Thanks for any help
Greg
--
View this message in context: http://old.nabble.com/transportConnectors-produce-into-http-consume-from-tcp-tp27951013p27951013.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: transportConnectors produce into http consume from tcp
Posted by Eibwen <gw...@sedonatek.com>.
Thanks, One of those times where a simple mistake breaks it, I had tried:
<transportConnectors>
<transportConnector name="openwire"
uri="tcp://localhost:61616?trace=true"/>
<transportConnector name="openwire" uri="http://localhost:8080?trace=true"
/>
</transportConnectors>
which caused exceptions obviously, i didn't read the name parameter closely
enough to realize that its just an identification label so it needs to be
unique. I had glanced at it and assumed it told what protocol to use.
tjsnell wrote:
>
> For example:
>
> <transportConnectors>
> <transportConnector name="tcp" uri="tcp://localhost:61616?trace=true"/>
> <transportConnector name="http" uri="http://localhost:8080?trace=true"
> />
> </transportConnectors>
>
--
View this message in context: http://old.nabble.com/transportConnectors-produce-into-http-consume-from-tcp-tp27951013p27988788.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: transportConnectors produce into http consume from tcp
Posted by Tracy Snell <ts...@gmail.com>.
On Mar 19, 2010, at 2:53 PM, Eibwen wrote:
> So i am wondering how can i setup the broker to allow both types of
> transports, or would i need two brokers running with a networkConnector
> between them?
You can setup as many types as you like in a broker, just assign each to a different port.
For example:
<transportConnectors>
<transportConnector name="tcp" uri="tcp://localhost:61616?trace=true"/>
<transportConnector name="http" uri="http://localhost:8080?trace=true" />
</transportConnectors>