tomee-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Romain Manni-Bucau <rmannibu...@gmail.com>
Subject Re: Embedded broker is not connecting full duplex to external broker
Date Mon, 28 Sep 2015 19:44:32 GMT
seems duplex is ignored on SimpleDiscoveryAgent and not set on
DiscoveryNetworkConnector with AMQ default factory.
see org.apache.activemq.transport.discovery.simple.SimpleDiscoveryAgentFactory#doCreateDiscoveryAgent

probably something to ask amq guys


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com>

2015-09-28 11:42 GMT-07:00 Jonathan S. Fisher <
jonathan@springventuregroup.com>:

> Hey guys,
>
> I have the following embedded broker configuration:
>
> <Resource
> id="ra/activemq"
> type="ActiveMQResourceAdapter">
> BrokerXmlConfig =
>
> broker:(vm://tomee1,network:static:(tcp://external-activemq-instance:61616)?duplex=true)?persistent=true&amp;brokerName=tomee1
> ServerUrl = vm://tomee1
> datasource =
> </Resource>
>
> When I look on the console for
> http://external-activemq-instance:8161/admin/network.jsp I do not see a
> bridge created for this connection. I *do* see a connection however on the
> http://external-activemq-instance:8161/admin/connections.jsp page.
>
> We can get activemq<-->activemq bridges to work bidirectionally no problem,
> it seems to be just the embedded broker. We need messages to flow in both
> directions. Any idea why this why this would be failing?
>
> *Jonathan S. Fisher*
>
> --
> Email Confidentiality Notice: The information contained in this
> transmission is confidential, proprietary or privileged and may be subject
> to protection under the law, including the Health Insurance Portability and
> Accountability Act (HIPAA). The message is intended for the sole use of the
> individual or entity to whom it is addressed. If you are not the intended
> recipient, you are notified that any use, distribution or copying of the
> message is strictly prohibited and may subject you to criminal or civil
> penalties. If you received this transmission in error, please contact the
> sender immediately by replying to this email and delete the material from
> any computer.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message