It might help if you could provide a minimal reproducer so anyone taking a look would see the actual broker config, know what client(s) are you using (might not matter), based on that know which protocol version(s) are in use (might matter more) etc. Perhaps there is a config issue someone could spot, or perhaps there is/was a bug and they can then reproduce. It might be worth trying newer versions for comparison too given there have been a number of releases since then.
Robbie On Mon, 16 Dec 2019 at 19:54, Kristofor Horst <kristof...@gmail.com> wrote: > > Hello, > > I am encountering issues with message persistence in Qpid 6.1.4 running on > RedHat 6.9. > > I have a LVQ with persistent messages set to ALWAYS, and when I provide a > message I can see it in the queue. When I cycle qpid, I lose this message > and it will not reappear in the queue even after the restart is finished and > all other communications are flowing again. > > This is a critical queue for the system so I would really appreciate help > with figuring out my issue. > > The queue itself is durable, LVQ, persistent = ALWAYS; The message comes in > marked as persistent when metadata is viewed. I have no issues with > sending/reading the queue except with restarting qpid dropping all the > messages and not recovering them. > > Broker is running as JSON node BDB host. > > I see no errors in my qpid.logs; all my permissions appear in order. > > Thanks, > Kristofor > > > > -- > Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org > For additional commands, e-mail: users-h...@qpid.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
