Hello, On Thu, 2013-04-25 at 23:08 +0000, Steve Huston wrote: > Have you obtained and built the persistence plugin from > QpidComponents.org? It sounds like maybe not. I'm not 100% sure which > branch/version matches your broker versions below, but I'd guess 0.18 and > 0.8. Hopefully someone with more detailed knowledge will chime in. >
This suggestion worked. I installed the following on Fedora 18 and Centos 6.3 respectively: - qpid-cpp-server-store-0.20-3.fc18.x86_64 - qpid-cpp-server-store-0.14-22.el6_3.x86_64 Et viola! The persistence starting working. I wish there were a detailed page explaining all that is necessary to use QPID persistence. A couple comments on the whole thing. The persistence is really slow on Fedora 18 with QPID 0.20. How ever the persistence is reasonable (if not slower than I would like) on Centos 6.3. QPID 0.14. Although the persistent queues and messages work in 0.20. flow-to-disk limit policy is not recognized. flow-to-disk policy is ignored with a warning message when QPID starts. I gather from this URL this is a known problem. - https://issues.apache.org/jira/browse/QPID-4339 I am not sure if the difference in performance is due to software (0.20 vs. 0.14). If so, 0.20 has regressed in performance. To be fair 0.14 is running on a server with 16 cores and 64 GB of memory. 0.20 is running on my laptop. 8 cores with 12 GB of memory. Thanks, Rob > -Steve > > On 4/25/13 6:18 PM, "Robert Seward" <[email protected]> wrote: > > >Hello, > > > >I have qpid 0.20 and 0.14 installed respectively on Fedora 18 and Centos > >6.2. RPM packages are as follows: > > > > - qpid-cpp-server-0.20-3.fc18.x86_64 > > - qpid-cpp-server-0.14-22.el6_3.x86_64 > > > >Both installations exhibit the same problem so this issue is likely one > >of a poor configuration on my part. The main problem is queues and > >messages do not survive restarts of the QPID process. > > > >I create (and recreate) my queues as follows: > > > > - qpid-config add queue $q --durable --file-count 64 --file-size 2560 > >--limit-policy flow-to-disk > > > >I use Python client libraries to create messages like this: > > > > conn = Connection("localhost:5672") > > conn.open() > > session = conn.session() > > sender = session.sender( "fetchQ" ) > > sender.send( Message("Persistent message of great value.", > >durable=True) ) > > > >My qpidd process is running as: > > [rseward@orthanc python]$ ps -ef | grep qpid > > qpidd 17118 1 0 12:00 ? 00:00:28 /usr/sbin/qpidd > >--data-dir /var/lib/qpidd --daemon > > > >The permissions on the data dir are as follows: > > [rseward@orthanc python]$ ls -ld /var/lib/qpidd > > drwxr-xr-x. 3 qpidd qpidd 4096 Jan 16 03:14 /var/lib/qpidd > > > >The queues are created and seem to be marked durable. Messages are > >queued and accumulated in the Persistent queue statistic counts, however > >neither the Queues or Messages survive the server restart. I must > >recreate the queues on every start. More over the data (messages) > >accumulated are lost. > > > >It is worth noting there is very little data being accumulated in the > >data-dir. > > > >I can provide additional information, but I am trying to be succinct in > >my initial e-mail regarding the problem. > > > >Thank you, > >Rob > > > >-- > >Rob Seward > >Curunir Consulting > > > >web: http://www.curunirconsulting.com/ > >e-mail: [email protected] > > > > > > > >--------------------------------------------------------------------- > >To unsubscribe, e-mail: [email protected] > >For additional commands, e-mail: [email protected] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
