[jira] [Created] (AMQ-4798) Destination limit for advisory topic very high after recent commit

["Claus Ibsen (JIRA)" <ji...@apache.org>]

Claus Ibsen created AMQ-4798:
--------------------------------

             Summary: 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
             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?
[10:59:29] 	 ssadeghi (~ssadeghi@ovpn-112-57.ams2.redhat.com) left IRC. (Ping timeout: 240 seconds)
[11:11:16] 	 Viral (~vgohel@dhcp223-58.pnq.redhat.com) joined the channel.
[11:11:35] 	 Viral is now known as Viral|Call
[11:15:45] 	 ssadeghi (~ssadeghi@ovpn-112-57.ams2.redhat.com) joined the channel.
[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)