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