You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2008/10/10 14:37:53 UTC
[jira] Updated: (AMQ-1973) Messages are lost if duplex is set to
"true"
[ https://issues.apache.org/activemq/browse/AMQ-1973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Tully updated AMQ-1973:
----------------------------
Description: With a network of brokers, Hub and Spoke, the spoke as a duplex network connector to the Hub. Regular producer on the Spoke, Consumer on the Hub. If there is a temp network outage (disconnect/reconnect cable) on the network connector between Spoke and Hub, persistent messages can get lost; acked but not dispatched. This only happens if the network connector isDuplex (was: With a network of brokers, Hub and Spoke, the spoke as a duplex network connector to the Hub. Regular producer on the Spoke, Consumer on the Hub. If there is a temp network outage (disconnect/reconnect cable) on the network connector between Spoke and Hub, persistent messages can get lots, but only if the network connector isDuplex)
> Messages are lost if duplex is set to "true"
> --------------------------------------------
>
> Key: AMQ-1973
> URL: https://issues.apache.org/activemq/browse/AMQ-1973
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.1.0
> Environment: all
> Reporter: Gary Tully
> Assignee: Gary Tully
> Fix For: 5.3.0
>
>
> With a network of brokers, Hub and Spoke, the spoke as a duplex network connector to the Hub. Regular producer on the Spoke, Consumer on the Hub. If there is a temp network outage (disconnect/reconnect cable) on the network connector between Spoke and Hub, persistent messages can get lost; acked but not dispatched. This only happens if the network connector isDuplex
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.