Re: Duplicate messages in queues
No - that wouldn't be the expected behaviour of queues... can you give a
little more information about your test scenario... which broker are you
using (Java or C++)?, how did you set up the queue? how are you verifying
that only one message is actually on the queue?
There are queue types (such as LVQs) which replace older versions of the
same message with newer ones... or there are ways of sending messages
which cause the messages to be discarded if no-one is listening to pick
them up. Without a few more details it's a bit difficult to explain
exactly what it is that you are seeing,
Cheers,
Rob
PS I see you tried to ask this question on the #qpid IRC channel yesterday
and didn't get any response... apologies - a lot of us are based in Europe
and so don't necessarily pick up stuff on there overnight.
On 13 June 2013 04:13, Ed Bragg ebr...@t-sciences.com wrote:
If I put the same TextMessage in a queue more than once, say 10 times, I
always end up with just one item in the queue.
ie. {query:apple}
Is this expected behavior for AMQP and Queues?
Regards,
Ed Bragg
--
---
Ed Bragg
iHarvest Product Manager
Principle Software Engineer
Thermopylae Sciences + Technology
e-mail: ebr...@t-sciences.com
cell: (540) 272-1866
office: (703) 740-8768
---
Re: Duplicate messages in queues
Hi Rob,
We are using the Java Broker. Version 0.20.
Right now we are running stock configuration (test).
I have a Java class that is popping items onto the queue, and then pulling
them all off until none are left.
I'm using a QueueProducer, and initializing it with:
Destination dest = null;
try {
dest = new AMQAnyDestination(ADDR: + queue + ; {
create:always });
} catch (URISyntaxException ex) {
logger.error(URI Syntax Exception: + ex.getMessage());
}
MessageProducer messageProducer = null;
try {
messageProducer = _session.createProducer(dest);
logger.info(Successfully created Producer: + dest.toString()
+ .);
} catch (JMSException ex) {
logger.error(JMS Exception: + ex.getMessage());
}
return new QueueProducer(_session, messageProducer );
I then pull them all off by creating a QueueConsumer, until
receive(timeout) returns null and output each message.
If I put in the queue:
apple
banana
cherry
durian
I get out:
cherry
banana
apple
durian
---
when I put in:
apple
apple
apple
apple
I get out:
apple
Ed
On Thu, Jun 13, 2013 at 3:42 AM, Rob Godfrey rob.j.godf...@gmail.comwrote:
No - that wouldn't be the expected behaviour of queues... can you give a
little more information about your test scenario... which broker are you
using (Java or C++)?, how did you set up the queue? how are you verifying
that only one message is actually on the queue?
There are queue types (such as LVQs) which replace older versions of the
same message with newer ones... or there are ways of sending messages
which cause the messages to be discarded if no-one is listening to pick
them up. Without a few more details it's a bit difficult to explain
exactly what it is that you are seeing,
Cheers,
Rob
PS I see you tried to ask this question on the #qpid IRC channel yesterday
and didn't get any response... apologies - a lot of us are based in Europe
and so don't necessarily pick up stuff on there overnight.
On 13 June 2013 04:13, Ed Bragg ebr...@t-sciences.com wrote:
If I put the same TextMessage in a queue more than once, say 10 times, I
always end up with just one item in the queue.
ie. {query:apple}
Is this expected behavior for AMQP and Queues?
Regards,
Ed Bragg
--
---
Ed Bragg
iHarvest Product Manager
Principle Software Engineer
Thermopylae Sciences + Technology
e-mail: ebr...@t-sciences.com
cell: (540) 272-1866
office: (703) 740-8768
---
--
---
Ed Bragg
iHarvest Product Manager
Principle Software Engineer
Thermopylae Sciences + Technology
e-mail: ebr...@t-sciences.com
cell: (540) 272-1866
office: (703) 740-8768
---
Re: Duplicate messages in queues
I apologize. I found where somebody on our end was shoving everything into
a HashSet.
Sorry for the confusion.
Ed
On Thu, Jun 13, 2013 at 3:22 PM, Ed Bragg ebr...@t-sciences.com wrote:
Hi Rob,
We are using the Java Broker. Version 0.20.
Right now we are running stock configuration (test).
I have a Java class that is popping items onto the queue, and then pulling
them all off until none are left.
I'm using a QueueProducer, and initializing it with:
Destination dest = null;
try {
dest = new AMQAnyDestination(ADDR: + queue + ; {
create:always });
} catch (URISyntaxException ex) {
logger.error(URI Syntax Exception: + ex.getMessage());
}
MessageProducer messageProducer = null;
try {
messageProducer = _session.createProducer(dest);
logger.info(Successfully created Producer: +
dest.toString() + .);
} catch (JMSException ex) {
logger.error(JMS Exception: + ex.getMessage());
}
return new QueueProducer(_session, messageProducer );
I then pull them all off by creating a QueueConsumer, until
receive(timeout) returns null and output each message.
If I put in the queue:
apple
banana
cherry
durian
I get out:
cherry
banana
apple
durian
---
when I put in:
apple
apple
apple
apple
I get out:
apple
Ed
On Thu, Jun 13, 2013 at 3:42 AM, Rob Godfrey rob.j.godf...@gmail.comwrote:
No - that wouldn't be the expected behaviour of queues... can you give a
little more information about your test scenario... which broker are you
using (Java or C++)?, how did you set up the queue? how are you verifying
that only one message is actually on the queue?
There are queue types (such as LVQs) which replace older versions of the
same message with newer ones... or there are ways of sending messages
which cause the messages to be discarded if no-one is listening to pick
them up. Without a few more details it's a bit difficult to explain
exactly what it is that you are seeing,
Cheers,
Rob
PS I see you tried to ask this question on the #qpid IRC channel yesterday
and didn't get any response... apologies - a lot of us are based in Europe
and so don't necessarily pick up stuff on there overnight.
On 13 June 2013 04:13, Ed Bragg ebr...@t-sciences.com wrote:
If I put the same TextMessage in a queue more than once, say 10 times, I
always end up with just one item in the queue.
ie. {query:apple}
Is this expected behavior for AMQP and Queues?
Regards,
Ed Bragg
--
---
Ed Bragg
iHarvest Product Manager
Principle Software Engineer
Thermopylae Sciences + Technology
e-mail: ebr...@t-sciences.com
cell: (540) 272-1866
office: (703) 740-8768
---
--
---
Ed Bragg
iHarvest Product Manager
Principle Software Engineer
Thermopylae Sciences + Technology
e-mail: ebr...@t-sciences.com
cell: (540) 272-1866
office: (703) 740-8768
---
--
---
Ed Bragg
iHarvest Product Manager
Principle Software Engineer
Thermopylae Sciences + Technology
e-mail: ebr...@t-sciences.com
cell: (540) 272-1866
office: (703) 740-8768
---
