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

Justin Ross resolved QPID-4805.
-------------------------------

    Resolution: Fixed
      Assignee: Justin Ross

http://svn.apache.org/viewvc?view=revision&revision=1478309

Thanks to Ernie Allen for providing the patch.
                
> qpid-config default journal parameters override qpidd.conf
> ----------------------------------------------------------
>
>                 Key: QPID-4805
>                 URL: https://issues.apache.org/jira/browse/QPID-4805
>             Project: Qpid
>          Issue Type: Bug
>          Components: Python Tools
>    Affects Versions: 0.22
>            Reporter: Justin Ross
>            Assignee: Justin Ross
>             Fix For: 0.23
>
>
> From Leonid:
> """
> The user can set default journal parameters (number of files and a size of 
> each file) in qpidd config file. These are the options 'num-jfiles' and 
> 'jfile-size-pgs', which are properly documented. The broker is supposed to 
> use these parameters while creating a new durable queue in case that no 
> journal parameters were provided by the client's application.
> The problem is that qpid-config tool sends values fileCount = 8, fileSize = 
> 24 to the broker if called without "--file-count" and "--file-size" 
> parameters.
> Imagine the situation where a user sets some default 'num-jfiles' and 
> 'jfile-size-pgs' values in qpidd config file and then creates a durable queue 
> using qpid-config tool: 'qpid-config add queue test --durable'. The resulting 
> queue's journal will have parameters fileCount = 8, fileSize = 24, which will 
> differ from the ones set by the user in config file.
> """

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to