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: [email protected]
For additional commands, e-mail: [email protected]
