Return-Path: Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: (qmail 31447 invoked from network); 27 Oct 2009 23:00:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 27 Oct 2009 23:00:56 -0000 Received: (qmail 27491 invoked by uid 500); 27 Oct 2009 21:14:16 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 27431 invoked by uid 500); 27 Oct 2009 21:14:16 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 27417 invoked by uid 99); 27 Oct 2009 21:14:16 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Oct 2009 21:14:16 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Oct 2009 21:14:14 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id D4B56234C046 for ; Tue, 27 Oct 2009 14:13:52 -0700 (PDT) Message-ID: <1299218141.1256678032867.JavaMail.jira@brutus> Date: Tue, 27 Oct 2009 14:13:52 -0700 (PDT) From: "Bruce Snyder (JIRA)" To: dev@activemq.apache.org Subject: [jira] Updated: (AMQ-2467) Confusion with changes to the default activemq.xml configuration file In-Reply-To: <1952168573.1256676472735.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: ae95407df07c98740808b2ef9da0087c X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/activemq/browse/AMQ-2467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Snyder updated AMQ-2467: ------------------------------ Attachment: AMQ-2467.patch.txt > 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 > > 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|http://svn.apache.org/viewvc?view=revision&revision=812481] commented out the {{}} element entirely. > * [Revision 812481|http://svn.apache.org/viewvc?view=revision&revision=812481] also set the default {{memoryLimit}} attribute on {{}} element to 20mb instead of the intended128mb. > * [Revision 813011|http://svn.apache.org/viewvc?view=revision&revision=813011] added back the {{memoryLimit}} attribute on {{}} 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 {{}} element to the {{}} element for all topics. There should be no pendingSubscriberPolicy by default. > * [Revision 820563|http://svn.apache.org/viewvc?view=revision&revision=820563] added a {{}} element to the {{}} 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 {{}} 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.