You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Ben Nisbet (JIRA)" <ji...@apache.org> on 2016/06/22 15:16:57 UTC
[jira] [Created] (AMQ-6334) ActiveMQConnection triggered heap space
out of memory error when used with
org.apache.activemq.network.SimpleJmsQueueConnector
Ben Nisbet created AMQ-6334:
-------------------------------
Summary: ActiveMQConnection triggered heap space out of memory error when used with org.apache.activemq.network.SimpleJmsQueueConnector
Key: AMQ-6334
URL: https://issues.apache.org/jira/browse/AMQ-6334
Project: ActiveMQ
Issue Type: Improvement
Components: Broker
Affects Versions: 5.10.2
Environment: WebLogic 10.3.6, JRockit JDK 1.6
Reporter: Ben Nisbet
Fix For: 5.12.1, 5.13.0
When using an OutboundQueueBridge associated with a SimpleJmsQueueConnector bean I have observed the default ReconnectionPolicy.maxSendRetries value of 10 to result in message loss if the connection to destination server is unreliable. (messages that are not delivered to destination within maxSendRetries are still acknowledged as having been consumed by processing of later messages)
Is it possible for the org.apache.activemq.network.jms.DestinationBridge.onMessage() implementation to interpret a ReconnectionPolicy.maxSendRetries property value of -1 as infinity?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)