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 2013/10/11 12:16:41 UTC
[jira] [Assigned] (AMQ-4798) Destination limit for advisory topic
very high after recent commit
[ https://issues.apache.org/jira/browse/AMQ-4798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Tully reassigned AMQ-4798:
-------------------------------
Assignee: Gary Tully
> Destination limit for advisory topic very high after recent commit
> ------------------------------------------------------------------
>
> Key: AMQ-4798
> URL: https://issues.apache.org/jira/browse/AMQ-4798
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.9.0
> Reporter: Claus Ibsen
> Assignee: Gary Tully
> Fix For: 5.9.0
>
>
> [10:58:42] <davsclaus> gtully on last amq from ASF i see this when starting the standalone broker
> [10:58:43] <davsclaus> INFO | Usage(default:memory:topic://ActiveMQ.Advisory.MasterBroker:memory) limit=720332416 should be smaller than its parent limit=720332390
> [10:58:54] <davsclaus> i guess its the recent 70% heap memory stuff
> [10:59:11] <davsclaus> just wonder if everyone will see this, and if we can make the message more friendly?
> [11:28:06] <rajdavies> davsclaus - why is the destination memory limit so high for an advisory ?
> [11:29:23] <davsclaus> rajdavies not sure - gtully changed the default settings yesterday instead of fixed 64mb limit etc
> [11:29:31] <davsclaus> it was 70% heap memory based instead
> [11:30:03] <dejanb> rajdavies: and per destination limit is removed … so I guess we have some bug in there
> [11:30:06] <davsclaus> http://git-wip-us.apache.org/repos/asf/activemq/commit/5bdcc196
> [11:30:39] <rajdavies> davsclaus - ok - looks like a bug then
--
This message was sent by Atlassian JIRA
(v6.1#6144)