You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by Luis Neves <lu...@co.sapo.pt> on 2006/12/28 13:42:00 UTC

Duplicate messages

Hello all,
Does anybody have a clue about what kind of Mina misconfiguration can lead to 
duplication of messages?
I have a server, a consumer and a producer, if the producer is fast enough the 
consumer receives a bunch of duplicate messages... any idea of what may cause 
this behaviour?

I have a small test case available here:
<http://websites.labs.sapo.pt/mina/MinaDuplicatesTestCase.zip>
When running this test case the number of received messages is greater than the 
number of produced messages.

I'm using "trunk".


--
Luis Neves


Re: Duplicate messages - FIXED

Posted by Trustin Lee <tr...@gmail.com>.
On 1/6/07, Luis Neves <lu...@co.sapo.pt> wrote:
>
> Luis Neves wrote:
> >
> > Hello all,
> > Does anybody have a clue about what kind of Mina misconfiguration can
> > lead to duplication of messages?
> > I have a server, a consumer and a producer, if the producer is fast
> > enough the consumer receives a bunch of duplicate messages... any idea
> > of what may cause this behaviour?
>
> I figure it out. In the decoder I was calling Buffer.rewind() but should
> be
> calling Buffer.position(start).


It's great to hear that you found the problem!

Trustin
-- 
what we call human nature is actually human habit
--
http://gleamynode.net/
--
PGP key fingerprints:
* E167 E6AF E73A CBCE EE41  4A29 544D DE48 FE95 4E7E
* B693 628E 6047 4F8F CFA4  455E 1C62 A7DC 0255 ECA6

Re: Duplicate messages - FIXED

Posted by Luis Neves <lu...@co.sapo.pt>.
Luis Neves wrote:
> 
> Hello all,
> Does anybody have a clue about what kind of Mina misconfiguration can 
> lead to duplication of messages?
> I have a server, a consumer and a producer, if the producer is fast 
> enough the consumer receives a bunch of duplicate messages... any idea 
> of what may cause this behaviour?

I figure it out. In the decoder I was calling Buffer.rewind() but should be 
calling Buffer.position(start).

--
Luis Neves