You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by jbelch <ja...@verizon.net> on 2013/07/30 20:46:10 UTC
Durable Last Value Queue
I am using Qpid Java Broker .20 and I am trying to persist messages for a
last value queue. I set the "durable" flag to true cycled the broker. When
I went to the management console, I noticed that the durable flag on the
queue was still set to false. I then came across the following statement
"LVQ does not support durable messages". Is this still the case for .22?
Will you ever be able to persist messages in a last value queue?
--
View this message in context: http://qpid.2158936.n2.nabble.com/Durable-Last-Value-Queue-tp7596176.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
RE: Durable Last Value Queue
Posted by Steve Huston <sh...@riverace.com>.
Hi James,
> -----Original Message-----
> From: jbelch [mailto:jamesbelch@verizon.net]
> Sent: Tuesday, July 30, 2013 4:03 PM
> To: users@qpid.apache.org
> Subject: Re: Durable Last Value Queue
>
> Is there a JMS property to set on the message to make the message
> durable?
Someone with JMS expertise will need to help with this one.
> In the C++ code, I found a qpid::messaging::Message.setDurable flag that
> doesn't seem to be persisting the data. I am using Berkeley DB as the
> message store.
Both the message durable flag and the queue that the message ends up in need to be durable to actually be stored.
-Steve
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Durable Last Value Queue
Posted by Rob Godfrey <ro...@gmail.com>.
Excellent - glad you could get it working... let us know if you have any
other issues.
-- Rob
On 31 July 2013 01:31, jbelch <ja...@verizon.net> wrote:
> I got it working. The virtualhosts.xml didn't like have multiple Berkeley
> DB
> store entries under different environments. I put it under the test
> environment only and it had no problems reloading the messages. Thanks for
> the quick response. The LVQ quote was from an older C++ word document and
> I
> could not find anything stating the Java Broker handled durable last value
> queues.
>
>
>
> --
> View this message in context:
> http://qpid.2158936.n2.nabble.com/Durable-Last-Value-Queue-tp7596176p7596216.html
> Sent from the Apache Qpid users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
Re: Durable Last Value Queue
Posted by jbelch <ja...@verizon.net>.
I got it working. The virtualhosts.xml didn't like have multiple Berkeley DB
store entries under different environments. I put it under the test
environment only and it had no problems reloading the messages. Thanks for
the quick response. The LVQ quote was from an older C++ word document and I
could not find anything stating the Java Broker handled durable last value
queues.
--
View this message in context: http://qpid.2158936.n2.nabble.com/Durable-Last-Value-Queue-tp7596176p7596216.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Durable Last Value Queue
Posted by Rob Godfrey <ro...@gmail.com>.
On 31 July 2013 00:45, Robbie Gemmell <ro...@gmail.com> wrote:
> 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?
>
>
In particular how are you creating the consumer for the messages on the
LVQ? What address string are you using? Are you using it as a topic or a
queue?
-- Rob
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 <ja...@verizon.net> 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: users-unsubscribe@qpid.apache.org
> > For additional commands, e-mail: users-help@qpid.apache.org
> >
> >
>
Re: Durable Last Value Queue
Posted by Robbie Gemmell <ro...@gmail.com>.
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 <ja...@verizon.net> 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: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
Re: Durable Last Value Queue
Posted by jbelch <ja...@verizon.net>.
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: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Durable Last Value Queue
Posted by Rob Godfrey <ro...@gmail.com>.
On 30 July 2013 22:02, jbelch <ja...@verizon.net> wrote:
> Is there a JMS property to set on the message to make the message durable?
>
You need to set the delivery mode either on the MessageProducer itself:
http://docs.oracle.com/javaee/6/api/javax/jms/MessageProducer.html#setDeliveryMode(int)
or you can use the follow version of send() to set it for each message you
publish:
http://docs.oracle.com/javaee/6/api/javax/jms/MessageProducer.html#send(javax.jms.Message,
int, int, long)
Note that the default mode is Persistent so absent any specific changing of
the delivery mode you do not actively need to change the mode to persistent.
-- Rob
> In the C++ code, I found a qpid::messaging::Message.setDurable flag that
> doesn't seem to be persisting the data. I am using Berkeley DB as the
> message store.
>
>
>
> --
> View this message in context:
> http://qpid.2158936.n2.nabble.com/Durable-Last-Value-Queue-tp7596176p7596182.html
> Sent from the Apache Qpid users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
Re: Durable Last Value Queue
Posted by jbelch <ja...@verizon.net>.
Is there a JMS property to set on the message to make the message durable?
In the C++ code, I found a qpid::messaging::Message.setDurable flag that
doesn't seem to be persisting the data. I am using Berkeley DB as the
message store.
--
View this message in context: http://qpid.2158936.n2.nabble.com/Durable-Last-Value-Queue-tp7596176p7596182.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Durable Last Value Queue
Posted by jbelch <ja...@verizon.net>.
I added the following to virtualhosts.xml
<queue>
<name>TestQueue</name>
<TestQueue>
<exchange>amq.direct</exchange>
<lvq>true</lvq>
<lvqKey>TestKey</lvqKey>
</TestQueue>
<durable>true</durable>
</queue>
I didn't realize the durable flag was outside fo the TestQueue element. I
moved it inside the TestQueue element and it works. Sorry for the
inconvenience.
--
View this message in context: http://qpid.2158936.n2.nabble.com/Durable-Last-Value-Queue-tp7596176p7596181.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Durable Last Value Queue
Posted by Rob Godfrey <ro...@gmail.com>.
Hi,
where did you see the statement that the LVQ does not support durable
messages? As far as I can recall there is no reason why an LVQ in the Java
Broker cannot hold durable messages
-- Rob
On 30 July 2013 20:46, jbelch <ja...@verizon.net> wrote:
> I am using Qpid Java Broker .20 and I am trying to persist messages for a
> last value queue. I set the "durable" flag to true cycled the broker.
> When
> I went to the management console, I noticed that the durable flag on the
> queue was still set to false. I then came across the following statement
> "LVQ does not support durable messages". Is this still the case for .22?
> Will you ever be able to persist messages in a last value queue?
>
>
>
> --
> View this message in context:
> http://qpid.2158936.n2.nabble.com/Durable-Last-Value-Queue-tp7596176.html
> Sent from the Apache Qpid users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>