activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dejan Bosanac (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AMQ-1894) Slim down the activemq.xml to focus on production config v. feature demonstration
Date Fri, 04 Sep 2009 13:15:14 GMT

     [ https://issues.apache.org/activemq/browse/AMQ-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dejan Bosanac updated AMQ-1894:
-------------------------------

    Attachment: configuration.patch

Attached patch (configuration.patch) is a proposal for new configuration files for 5.3.0.

First of all it trims down the default configuration as Bruce proposed. I also set kahaDB
as a default persistence mechanism for 5.3.0.

Next we have camel and jetty configurations pulled out into separate configuration files activemq-camel.xml
and activemq-jetty.xml so that they can be easily imported into other configuration files.

Currently inclusion of both of these files are commented in default configuration and I guess
the first question is whether we want to keep it that way.

activemq-demo.xml is pretty much the same as the current configuration file, but with kahaDB
and producer flow control explicitly turned on.

I created some more configuration examples. They are all located assembly/src/sample-conf.
I renamed and modified some of the existing ones (network examples - thanks Andreas) and added
some more. All files with activemq-*.xml pattern from that folder are included into conf folder
of the distribution. There are some other files there, that I think are outdated, so we should
probably remove them (another debating question)

Here is the list of new configuration examples:

activemq-jdbc.xml - demonstrates jdbc storage
activemq-security- demonstrates secured broker
activemq-command - demonstrates command agent and xmpp protocol
activemq-static-network-broker1.xml and activemq-static-network-broker2.xml - demonstrates
static network setup
activemq-dynamic-network-broker1.xml and activemq-dynamic-network-broker2.xml - demonstrates
multicast network setup

shared file system master slave can be demonstrated using the default configuration file.

What would be good to have as well:

activemq-scalability.xm and activemq-throughput.xml

which will show how to tune broker for these two use cases. I'll start working on them now.

Please post your comments on these. If there are no major objections, we can start by committing
this patch and working further on polishing them up. More comments in the files and wiki documentation
would be great.

Cheers


> Slim down the activemq.xml to focus on production config v. feature demonstration 
> ----------------------------------------------------------------------------------
>
>                 Key: AMQ-1894
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1894
>             Project: ActiveMQ
>          Issue Type: Improvement
>    Affects Versions: 5.1.0
>            Reporter: Bruce Snyder
>            Assignee: Dejan Bosanac
>             Fix For: 5.3.0
>
>         Attachments: activemq-demo.xml.diff.txt, activemq.xml.diff.txt, configuration.patch,
SampleConfigs.zip
>
>
> I have slimmed down the default activemq.xml so it focuses more on a minimal production
style configuration instead of a demonstration of features. My thoughts on this are that the
goal of providing a good default config and the goal of demonstrating features should be represented
separately. This is as simple as paring down the amount of items in the default XML config
and moving some of the items that demonstrate what you can do in the XML config to a separate
config file. I've also done this and named the feature demo config activemq-demo.xml. I've
also added many more comments to further document each config option. Attached are the diffs.


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


Mime
View raw message