You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Bruce Snyder (JIRA)" <ji...@apache.org> on 2008/08/18 18:13:52 UTC

[jira] Created: (AMQ-1894) Slim down the activemq.xml to focus on production config v. feature demonstration

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
             Fix For: 5.2.0
         Attachments: activemq.xml.diff.txt

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.


[jira] Updated: (AMQ-1894) Slim down the activemq.xml to focus on production config v. feature demonstration

Posted by "Dejan Bosanac (JIRA)" <ji...@apache.org>.
     [ 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.


[jira] Commented: (AMQ-1894) Slim down the activemq.xml to focus on production config v. feature demonstration

Posted by "Bruce Snyder (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/AMQ-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54033#action_54033 ] 

Bruce Snyder commented on AMQ-1894:
-----------------------------------

I like the idea of including many more configuration examples. I see lot of opportunity to provide users good configuration examples that support various use cases here. 

I think that we should probably split up these configs into separate directories with a README file for each directory. The README file should explain how to run the broker using the config and what behavior to expect from the broker. It should also include information on how to exercise the various features for that configuration. This would mean that we would need to provide various examples of test clients, etc., but I think that work would be very good for users. 

Since there's already an examples directory, I think we should move this work into that directory and have a separate directory for each use case. There's no need to create another directory in the ActiveMQ base directory. Let's just use what's already there. 

> 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.


[jira] Updated: (AMQ-1894) Slim down the activemq.xml to focus on production config v. feature demonstration

Posted by "Bruce Snyder (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQ-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bruce Snyder updated AMQ-1894:
------------------------------

    Attachment:     (was: AMQ-1894.patch.txt)

> 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, 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.


[jira] Updated: (AMQ-1894) Slim down the activemq.xml to focus on production config v. feature demonstration

Posted by "Bruce Snyder (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQ-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bruce Snyder updated AMQ-1894:
------------------------------

    Attachment:     (was: activemq.xml.diff.txt)

> 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
>             Fix For: 5.2.0
>
>         Attachments: activemq-demo.xml.diff.txt, activemq.xml.diff.txt
>
>
> 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.


[jira] Updated: (AMQ-1894) Slim down the activemq.xml to focus on production config v. feature demonstration

Posted by "Bruce Snyder (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQ-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bruce Snyder updated AMQ-1894:
------------------------------

    Fix Version/s:     (was: 5.4.0)
                   5.3.0

> 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: Rob Davies
>             Fix For: 5.3.0
>
>         Attachments: activemq-demo.xml.diff.txt, activemq.xml.diff.txt
>
>
> 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.


[jira] Updated: (AMQ-1894) Slim down the activemq.xml to focus on production config v. feature demonstration

Posted by "Bruce Snyder (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQ-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bruce Snyder updated AMQ-1894:
------------------------------

    Attachment:     (was: activemq-demo.xml.diff.txt)

> 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
>             Fix For: 5.2.0
>
>         Attachments: activemq-demo.xml.diff.txt, activemq.xml.diff.txt
>
>
> 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.


[jira] Updated: (AMQ-1894) Slim down the activemq.xml to focus on production config v. feature demonstration

Posted by "Bruce Snyder (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQ-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bruce Snyder updated AMQ-1894:
------------------------------

    Attachment: activemq-demo.xml.diff.txt

> 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
>             Fix For: 5.2.0
>
>         Attachments: activemq-demo.xml.diff.txt, activemq.xml.diff.txt
>
>
> 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.


[jira] Assigned: (AMQ-1894) Slim down the activemq.xml to focus on production config v. feature demonstration

Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQ-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Davies reassigned AMQ-1894:
-------------------------------

    Assignee: Rob Davies

> 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: Rob Davies
>             Fix For: 5.3.0
>
>         Attachments: activemq-demo.xml.diff.txt, activemq.xml.diff.txt
>
>
> 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.


[jira] Updated: (AMQ-1894) Slim down the activemq.xml to focus on production config v. feature demonstration

Posted by "Bruce Snyder (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQ-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bruce Snyder updated AMQ-1894:
------------------------------

    Attachment: activemq-demo.xml.diff.txt

> 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
>             Fix For: 5.2.0
>
>         Attachments: activemq-demo.xml.diff.txt, activemq.xml.diff.txt
>
>
> 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.


[jira] Updated: (AMQ-1894) Slim down the activemq.xml to focus on production config v. feature demonstration

Posted by "Gary Tully (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQ-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully updated AMQ-1894:
----------------------------

    Fix Version/s: 5.3.0
                       (was: 5.2.0)

> 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
>             Fix For: 5.3.0
>
>         Attachments: activemq-demo.xml.diff.txt, activemq.xml.diff.txt
>
>
> 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.


[jira] Commented: (AMQ-1894) Slim down the activemq.xml to focus on production config v. feature demonstration

Posted by "Andreas Gies (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/AMQ-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=53990#action_53990 ] 

Andreas Gies commented on AMQ-1894:
-----------------------------------

I have published a blog recently for enabling security for the webapps in the embedded jetty, might be interesting as well. 

http://open-source-adventures.blogspot.com/2009/09/enabling-security-for-activemq-web-apps.html



> 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: Bruce Snyder
>             Fix For: 5.3.0
>
>         Attachments: activemq-demo.xml.diff.txt, activemq.xml.diff.txt, 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.


[jira] Commented: (AMQ-1894) Slim down the activemq.xml to focus on production config v. feature demonstration

Posted by "Gary Tully (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/AMQ-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54057#action_54057 ] 

Gary Tully commented on AMQ-1894:
---------------------------------

I think "conf" is the place for these well named configuration files.

Comments "in line" in the configuration files may be best as this will be closest to the relevant config and will be easiest to maintain. Longer term, keeping any more than a single file in sync will be difficult.


> 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.


[jira] Assigned: (AMQ-1894) Slim down the activemq.xml to focus on production config v. feature demonstration

Posted by "Bruce Snyder (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQ-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bruce Snyder reassigned AMQ-1894:
---------------------------------

    Assignee: Bruce Snyder  (was: Rob Davies)

> 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: Bruce Snyder
>             Fix For: 5.3.0
>
>         Attachments: activemq-demo.xml.diff.txt, activemq.xml.diff.txt
>
>
> 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.


[jira] Updated: (AMQ-1894) Slim down the activemq.xml to focus on production config v. feature demonstration

Posted by "Bruce Snyder (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQ-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bruce Snyder updated AMQ-1894:
------------------------------

    Attachment: activemq.xml.diff.txt

> 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
>             Fix For: 5.2.0
>
>         Attachments: activemq.xml.diff.txt
>
>
> 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.


[jira] Updated: (AMQ-1894) Slim down the activemq.xml to focus on production config v. feature demonstration

Posted by "Bruce Snyder (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQ-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bruce Snyder updated AMQ-1894:
------------------------------

    Attachment: AMQ-1894.patch.txt

> 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, 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.


[jira] Updated: (AMQ-1894) Slim down the activemq.xml to focus on production config v. feature demonstration

Posted by "Bruce Snyder (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQ-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bruce Snyder updated AMQ-1894:
------------------------------

    Attachment: activemq.xml.diff.txt

> 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
>             Fix For: 5.2.0
>
>         Attachments: activemq-demo.xml.diff.txt, activemq.xml.diff.txt
>
>
> 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.


[jira] Commented: (AMQ-1894) Slim down the activemq.xml to focus on production config v. feature demonstration

Posted by "Dejan Bosanac (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/AMQ-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54056#action_54056 ] 

Dejan Bosanac commented on AMQ-1894:
------------------------------------

I added these files to the "conf" folder since that's the place most users will start looking for the configuration stuff. I think we can have all these files in one directory and covered with one README file, since there will be 5-6 files at most. Making a lot of folders with one (or two files) will just add to the complexity. I think we can use the default README.txt with the pointer to the site page, like it was done for code examples. All other improvement can be made later on.

> 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.


[jira] Commented: (AMQ-1894) Slim down the activemq.xml to focus on production config v. feature demonstration

Posted by "Dejan Bosanac (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/AMQ-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54062#action_54062 ] 

Dejan Bosanac commented on AMQ-1894:
------------------------------------

Added scalability configuration and made initial commit. As Garry pointed out, added all necessary comment directly in the configuration file. Reviews and comments more then welcomed. 

> 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.


[jira] Resolved: (AMQ-1894) Slim down the activemq.xml to focus on production config v. feature demonstration

Posted by "Dejan Bosanac (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQ-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dejan Bosanac resolved AMQ-1894.
--------------------------------

    Resolution: Fixed

Added activemq-throughput.xml, changed some default kahadb params to make default configuration fast enough without tweaking any persistence options. Web consoles (and APIs) are now enabled by default in a default config. All configs should be well commented and ready to go.

> 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.


[jira] Updated: (AMQ-1894) Slim down the activemq.xml to focus on production config v. feature demonstration

Posted by "Andreas Gies (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQ-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andreas Gies updated AMQ-1894:
------------------------------

    Attachment: SampleConfigs.zip

I have attached some config files for standard use cases that are more or less used in production:

standalone broker
static network
dynamic network
hot-hot configuration (network of brokers with 2 master/slave nodes)



> 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: Bruce Snyder
>             Fix For: 5.3.0
>
>         Attachments: activemq-demo.xml.diff.txt, activemq.xml.diff.txt, 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.


[jira] Assigned: (AMQ-1894) Slim down the activemq.xml to focus on production config v. feature demonstration

Posted by "Dejan Bosanac (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQ-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dejan Bosanac reassigned AMQ-1894:
----------------------------------

    Assignee: Dejan Bosanac  (was: Bruce Snyder)

> 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, 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.