I'm getting the same behavior using networkConnector as well. Here is the
setup I'm currently trying (I switched to using vm://localhost.)
<transportConnectors>
<transportConnector name="bxtpc" uri="vm://localhost"/>
</transportConnectors>
<networkConnectors>
<networkConnector uri="static:(tcp://10.10.10.2:61616)"/>
</networkConnectors>
This one is clearly connecting as well:
17:32:19,530 INFO [DiscoveryNetworkConnector] Establishing network
connection from vm://localhost?async=false&network=true to
tcp://10.10.10.2:61616
17:32:19,753 INFO [DemandForwardingBridgeSupport] Network connection
between vm://localhost and tcp:///10.10.10.2:61616@40224(soaqa002) has been
established.
Seems like the bridge is connected. I can see every other request hitting
break points in DemandForwardingBridgeSupport, but half the request never
do.
Any input is appreciated.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/JMS-Bridge-trying-to-copy-all-messages-to-remote-server-tp4659769p4659787.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
