From Gordon Sim: [gordon@mrg15 ~]$ qpid-config add queue --durable test-queue --max-queue-count 5 --limit-policy flow-to-disk --file-count 16 --file-size 1000 Failed: ((501, u'Queue test-queue: create() failed: jexception 0x0500 lpmgr::initialize() threw JERR_LFMGR_BADAEFNUMLIM: Bad auto-expand file number limit. (_ae_max_jfiles=0; num_jfiles=16) (MessageStoreImpl.cpp:456)'),) The error message isn't terribly helpful if so.
The framework for auto-expand has been added to the code, although the core of the auto-expand remains to be completed. This framework includes the handling of the command-line parameters for AE. At present, AE is enabled by default, with a auto-expand limit of 16 files (double the default of 8 files). The above example shows that leaving the parameter checking for options that are hidden is an error. In this case, the max auto-expand parameter being set to 16 files requires that the number of journal files be less than this. I have set auto-expand to false for now, this should prevent this from happening until auto-expand is completed. I have also fixed some of the logic around the checking of this parameter, and made the error message more useful (hopefully). Fixed in r.3525 QA: This bug is easily reproduced as shown above.
Changing target milestone to 1.2, as this was included in store backport for 1.2.
Tested: on -26 bug aapears on -28 has been fixed validated on RHEL5-Server-U4/RHEL4-U8 for archs i386/x86_64 packages: # rpm -qa | grep -E '(qpid|openais|rhm)' | sort -u openais-0.80.6-8.el5 python-qpid-0.5.752581-3.el5 qpidc-0.5.752581-28.el5 qpidc-debuginfo-0.5.752581-28.el5 qpidc-devel-0.5.752581-28.el5 qpidc-rdma-0.5.752581-28.el5 qpidc-ssl-0.5.752581-28.el5 qpidd-0.5.752581-28.el5 qpidd-acl-0.5.752581-28.el5 qpidd-cluster-0.5.752581-28.el5 qpidd-devel-0.5.752581-28.el5 qpid-dotnet-0.4.738274-2.el5 qpidd-rdma-0.5.752581-28.el5 qpidd-ssl-0.5.752581-28.el5 qpidd-xml-0.5.752581-28.el5 qpid-java-client-0.5.751061-9.el5 qpid-java-common-0.5.751061-9.el5 rhm-0.5.3206-14.el5 rhm-docs-0.5.756148-1.el5 rh-tests-distribution-MRG-Messaging-qpid_common-1.5-15 ->VERIFIED
Release note added. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Set parameter auto-expand to false for now, this should prevent this error from happening until auto-expand is completed. Also fixed some of the logic around the checking of file-count parameter, and made the error message more useful (514568)
Release note updated. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1,8 @@ -Set parameter auto-expand to false for now, this should prevent this error from happening until auto-expand is completed. Also fixed some of the logic around the checking of file-count parameter, and made the error message more useful (514568)+Messaging bug fix + +C: Using python tools to create a queue containing sixteen or more journal files +C: The broker would throw an error with a confusing error message and the queue creation would fail +F: The auto-expand parameter was set to false by default, the logic around the file-count parameter was improved, and the error message has been updated to be more meaningful. +R: The number of files is no longer limited, and the queue creation occurs as expected. + +Using python tools to create a queue containing sixteen or more journal files would result in the broker throwing a confusing error, and and the queue creation failing. The auto-expand parameter was set to false by default, the logic around the file-count parameter was improved, and the error message has been updated to be more meaningful. The number of files is no longer limited, and the queue creation occurs as expected.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2009-1633.html