The first log message indicates that the store has a 'queue entry' recording a persistent message being present on a particular durable queue, but during recovery that queue has not been found to exist. A possible reason for this would be removing a queue that was specified in the config file while the store still had record of messages being on it.
The second log message indicates that the store contains a persistent message which hasn't been assigned to *any* queue during recovery, and so the message will be removed from the store as a result. This log message is likely to follow the above unless the message happened to exist on multiple queues and some remained. Can you provide more detail on what you did leading up to seeing this? Can you reproduce the behaviour now, or starting from scratch? Finally, going back to Rob's first reply, using Google I see "LVQ does not support durable messages" being mentioned in the C++ broker docs (and a stale older copy of that on the wiki), I presume you were looking at one of those originally? Robbie On 30 July 2013 22:53, jbelch <[email protected]> wrote: > It looks like Berkeley DB is storing the messages in the .jdb binary file. > When I cycle the broker, I see the following WARN messages in the log: > > Message id 1 in log references queue with id > ea4Id34a-352c-329d-a877-485b02215a7b which is not in the configuration, > entry will be discarded > > Message id 1 in store, but not in any queue - removing.... > > Any ideas? > > > > -- > View this message in context: > http://qpid.2158936.n2.nabble.com/Durable-Last-Value-Queue-tp7596176p7596207.html > Sent from the Apache Qpid users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
