Excellent - glad you could get it working... let us know if you have any
other issues.
-- Rob
On 31 July 2013 01:31, jbelch 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
> environm
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
On 31 July 2013 00:45, Robbie Gemmell 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 remov
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
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 i
On 30 July 2013 22:02, jbelch 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
Hi James,
> -Original Message-
> From: jbelch [mailto:jamesbe...@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 exper
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.nabb
I added the following to virtualhosts.xml
TestQueue
amq.direct
true
TestKey
true
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 me
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 wrote:
> I am using Qpid Java Broker .20 and I am trying to persist me
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
"
If we run 2 or 3 nodes in a cluster with mirrored HA queues, are there any
restrictions or special procedures that must be observed to upgrade the qpid
version on individual nodes without any service interruption? Can different
nodes in the cluster run different versions of qpid or do all the no
12 matches
Mail list logo
