[
https://issues.apache.org/activemq/browse/AMQ-2467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Snyder updated AMQ-2467:
------------------------------
Patch Info: [Patch Available]
Description:
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|http://svn.apache.org/viewvc?view=revision&revision=812481]
commented out the {{<systemUsage>}} element entirely.
* [Revision 812481|http://svn.apache.org/viewvc?view=revision&revision=812481]
also set the default {{memoryLimit}} attribute on {{<systemUsage>}} element to
20mb instead of the intended128mb.
* [Revision 813011|http://svn.apache.org/viewvc?view=revision&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|http://svn.apache.org/viewvc?view=revision&revision=819520]
added a {{<pendingSubscriberPolicy>}} element to the {{<policyEntry>}} element
for all topics. There should be no pendingSubscriberPolicy by default.
* [Revision 820563|http://svn.apache.org/viewvc?view=revision&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.
was:
Evidently some of the changes to the default configuration from AMQ-1894 got
crossed resulting in some undesirable changes including:
* [Revision 812481|http://svn.apache.org/viewvc?view=revision&revision=812481]
commented out the {{<systemUsage>}} element entirely.
* [Revision 812481|http://svn.apache.org/viewvc?view=revision&revision=812481]
also set the default {{memoryLimit}} attribute on {{<systemUsage>}} element to
20mb instead of the intended128mb.
* [Revision 813011|http://svn.apache.org/viewvc?view=revision&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|http://svn.apache.org/viewvc?view=revision&revision=819520]
added a {{<pendingSubscriberPolicy>}} element to the {{<policyEntry>}} element
for all topics. There should be no pendingSubscriberPolicy by default.
* [Revision 820563|http://svn.apache.org/viewvc?view=revision&revision=820563]
added a {{<pendingSubscriberPolicy>}} element to the {{<policyEntry>}} element
for all queues. There should be no pendingSubscriberPolicy by default.
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. It also looks like some of the docs
got goofed up so I'll fix that, too.
This issue is to remedy these items using a new patch.
> Confusion with changes to the default activemq.xml configuration file
> ----------------------------------------------------------------------
>
> Key: AMQ-2467
> URL: https://issues.apache.org/activemq/browse/AMQ-2467
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.3.0
> Reporter: Bruce Snyder
> Assignee: Bruce Snyder
> Fix For: 5.4.0
>
>
> 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|http://svn.apache.org/viewvc?view=revision&revision=812481] commented
> out the {{<systemUsage>}} element entirely.
> * [Revision
> 812481|http://svn.apache.org/viewvc?view=revision&revision=812481] also set
> the default {{memoryLimit}} attribute on {{<systemUsage>}} element to 20mb
> instead of the intended128mb.
> * [Revision
> 813011|http://svn.apache.org/viewvc?view=revision&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|http://svn.apache.org/viewvc?view=revision&revision=819520] added a
> {{<pendingSubscriberPolicy>}} element to the {{<policyEntry>}} element for
> all topics. There should be no pendingSubscriberPolicy by default.
> * [Revision
> 820563|http://svn.apache.org/viewvc?view=revision&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.
