activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <>
Subject [jira] Commented: (AMQ-2467) Confusion with changes to the default activemq.xml configuration file
Date Wed, 28 Oct 2009 13:07:52 GMT


Gary Tully commented on AMQ-2467:

Am thinking that producerFlowControll should be off by default. It is an advanced option that
allows producers to block such that the entire queue does not block on the broker side. So
it is relevant when blocking is the desired behavior.

I think the default should be to use disk space rather than to block. Blocking should only
happen when disk space is exhausted. To enable this, the pending message policy needs to be
configured to spool message indexes to disk.

>From my experience, producer flow control is experienced as "this broker is getting slower"
where as it should be experienced as the solution to: I have configured a queue limit but
I don't want to block all producers, just fast ones. Disabling it by default will lead users
to it when they need it.

> Confusion with changes to the default activemq.xml configuration file 
> ----------------------------------------------------------------------
>                 Key: AMQ-2467
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.3.0
>            Reporter: Bruce Snyder
>            Assignee: Bruce Snyder
>             Fix For: 5.4.0
>         Attachments: AMQ-2467.patch.txt
> The original intent of AMQ-1894 was to make the default configuration more production
ready instead of a demonstration of features. Evidently some of the changes to the default
configuration from AMQ-1894 got crossed resulting in some undesirable changes including: 
> * [Revision 812481|] commented
out the {{<systemUsage>}} element entirely. 
> * [Revision 812481|] also
set the default {{memoryLimit}} attribute on {{<systemUsage>}} element to 20mb instead
of the intended128mb. 
> * [Revision 813011|] added
back the {{memoryLimit}} attribute on {{<policyEntry>}} elements that apply to all destiations
after this attribute had been removed entirely in the original patch. 
> * [Revision 819520|] added
a {{<pendingSubscriberPolicy>}} element to the {{<policyEntry>}} element for all
topics. There should be no pendingSubscriberPolicy by default. 
> * [Revision 820563|] added
a {{<pendingSubscriberPolicy>}} element to the {{<policyEntry>}} element for all
queues. There should be no pendingSubscriberPolicy by default. 
> * It also looks like some of the docs got goofed up so I'll fix that, too. 
> * There are also three web applications enabled that shouldn't be including camel, demo
and fileserver 
> ** Enabling the camel web application also enables the camel JMX support which just confuses
users who notice the camel JMX domain is present 
> The original patch for AMQ-1894 removed the {{<destinationPolicy>}} element entirely.
At a later time it was agreed that it should be put back in but only to explicitly enable
producer flow control. 
> This issue is to remedy these items using a new patch. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message