I have two 5.1 brokers connecting okay over http transports. Could it be a firewall-related issue?
Joe Goto www.ttmsolutions.com for a free ActiveMQ user guide j0llyr0g3r wrote: > > Hey folks, > > i am having a hard time figuring out how to get http-tunneling working. > > According to the documentation from here: > http://activemq.apache.org/http-and-https-transports-reference.html > > this should be quite easy. > > Ok, so i set up broker "1" nice and easy (one inbound connector for > jms-clients, one http for the other broker and one http for the > network-connection): > > <transportConnectors> > <transportConnector name="inbound_openwire" > uri="tcp://localhost:61616"/> > <transportConnector name="inbound_http" > uri="http://localhost:61617"/> > </transportConnectors> > > <networkConnectors> > <networkConnector name="outbound_http" > uri="static://(http://esf-proto-2:61617)?trace=true" networkTTL="5"/> > </networkConnectors> > > Broker 2: > > <transportConnectors> > <transportConnector name="inbound_openwire" > uri="tcp://localhost:61616"/> > <transportConnector name="inbound_http" > uri="http://localhost:61617"/> > </transportConnectors> > > <networkConnectors> > <networkConnector name="outbound_http" > uri="static://(http://esf-proto-1:61617)?trace=true" networkTTL="5"/> > > </networkConnectors> > > As far as i can tell, this should work..... > > Unfortunately, it doesn't. > > Both brokers tell me on start-up: > > WARN DiscoveryNetworkConnector - Could not start network bridge > between: vm://localhost and: http://esf-proto-1:61617 due to: > java.net.ConnectException: Connection refused > INFO DemandForwardingBridge - localhost bridge to Unknown stopped > INFO DiscoveryNetworkConnector - Establishing network connection > between from vm://localhost to http://esf-proto-1:61617 > > > Now you could say that i obviously have some kind of typo or something > like that in my configuration, BUT: > > If i exchange http with tcp: > > s/http/tcp/g > > in the above shown configuration, everything works fine. > > So this is definitely a http-issue and not an error in my configuration. > > What am i doing wrong? > > The error message is confusing...... > > Has anybody a working configuration with http? > > I read in a mailing-list posting that AMQ uses jetty for http-traffic ( > not only for the admin console) but i am not sure about that.... > > Any ideas? > > -- View this message in context: http://www.nabble.com/Standard-http-connector-example-not-working--tp16937377s2354p16939141.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
