You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2015/06/09 16:15:03 UTC
[jira] [Resolved] (AMQ-5830) Broker duplex network connection is
shutdown when "javax.jms.ResourceAllocationException: Usage Manager memory
limit" is sent across the network
[ https://issues.apache.org/jira/browse/AMQ-5830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Tully resolved AMQ-5830.
-----------------------------
Resolution: Fixed
http://git-wip-us.apache.org/repos/asf/activemq/commit/31009090
setting network property on connection info was missing on the inbound vm transport.
> Broker duplex network connection is shutdown when "javax.jms.ResourceAllocationException: Usage Manager memory limit" is sent across the network
> ------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-5830
> URL: https://issues.apache.org/jira/browse/AMQ-5830
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, networkbridge
> Affects Versions: 5.11.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Fix For: 5.12.0
>
>
> With "sendFailIfNoSpaceAfterTimeout" or "sendFailIfNoSpace" is configured, producer flow control will send a javax.jms.ResourceAllocationException.
> This message is not supposed to be sent across the broker network.
> In a duplex network connection, the javax.jms.ResourceAllocationException is being sent across the network. This exception is received by the peer broker and the peer broker will subsequently shutdown the network connection.
> Note: it only seems to happen if the javax.jms.ResourceAllocationException is thrown from the broker that has the duplex network connector configured.
> Potential workaround: use non duplex network connectors ( one defined on each peer broker)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)