Tim Bain wrote
> all the examples I'm used to seeing use either static:, failover:, or
> masterslave: protocols to wrap the tcp: protocol for their
> networkConnectors. Can you try using "static:(tcp:" + REMOTE_BROKER_URL +
> ")" when creating your ActiveMQConnectionFactory and see if the behavior
> changes?
I'm not sure what you are asking me to do. That particular networkConnector
works (publish2EmbeddedBroker = false). It's the other path that uses the
embedded broker ("vm://" + EMBEDDED_BROKER_NAME) that's not working
(publish2EmbeddedBroker = true). you will note that the embedded broker's
networkConnection uses the format you specify.
Perhaps copying this code and and running it locally might better
demonstrate the problem? Is there a better way to share code than in a post,
like an attached zip file?
Here's the latest incarnations of PublishTopicTest and SubscribeTopicTest:
Tim Bain wrote
> Also, your current setup doesn't provide fault tolerance for the
> standalone
> broker itself. Do you need it to?
thanks for hanging in here with me
-----
Regards, Shackman
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Persistent-messages-not-moving-from-embedded-broker-to-remote-broker-tp4702884p4702998.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
