Hi Kristofor,
As Alex says, to me this looks like a problem with your environment
configuration / test set up - I cannot reproduce the issue you are seeing.
I downloaded Qpid 6.1.4, set up a virtual host as you described (JSON node,
BDB host) and a durable LVQ, with persist ALWAYS. I sent a message, ran
qpid.stop and restarted the broker. The message survived the broker
restart and was available for consumption.
-- Rob
On Thu, 19 Dec 2019 at 16:34, Oleksandr Rudyy <oru...@gmail.com> wrote:
> Hi Kristofor,
>
> The broker with provided virtual host and queue configuration should
> persist all published messages into message store and recover them on
> re-start.
> The fact that VirtualHost recovers all messages on its own re-start
> confirms the expected broker behaviour.
>
> It looks to me that you might have an issue with the storage. Could it be
> that the path to the message store changes between the restarts?
>
> Are you running Qpid broker in the container like docker?
>
> Kind Regards,
> Alex
>
>
>
>
> On Thu, 19 Dec 2019 at 14:46, Kristofor Horst <kristof...@gmail.com>
> wrote:
>
> > Robbie Gemmell wrote
> > > It might help if you could provide a minimal reproducer
> >
> > I think this will do it - I can't copy from a file so I have to hand type
> > it
> > - apologies.
> >
> > *
> > {
> > "storepath":"path/to/qpid/etc/example/config",
> > "desiredState":"active",
> > "name":"example",
> > "context":{},
> > "modelVersion":"6.1",
> > "type":"BDB",
> > "exchanges":[{ "name":"amq.topic", "type":"topic",
> > "bindings":[{
> > "name": "PersistentLVQTester",
> > "type":"binding", "durable" :true,
> > "queue" : "PersistentLVQTester"
> > }]
> > }],
> > "queues":[{"messageGroupsSharedGroups":false,
> > "LVQKey":"PersistentLVQTopicKey",
> > "holdOnPublishEnabled":false,
> > "messageDurability":"ALWAYS",
> > "type":"lvq",
> > "durable":true,
> > "name":"PersistentLVQTester"
> > }]
> > }
> > *
> >
> >
> > Robbie Gemmell wrote
> > > It might be worth trying newer versions for
> > > comparison too given there have been a number of releases since then.
> >
> > Unfortunately not an option for my use case. I am restricted to this
> > version, which is already a massive improvement from 0.20 that we were
> > using
> > before!
> >
> > I was able to make limited progress with messages persisting when the
> > virtualhost node of the broker is cycled via the UI. The message will
> > correctly reappear if the node is stopped and started through the
> > interface.
> > However, we'd like to be able to cycle the broker itself using the
> > qpid.stop
> > script file and have the messages persisted.
> >
> > Is this feasible or a misinterpretation of the system functionality?
> >
> >
> >
> >
> >
> > --
> > 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
> >
> >
>
