[ 
https://issues.apache.org/activemq/browse/AMQ-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Johnny reopened AMQ-1936:
-------------------------

    Regression: [Broken Unit Test]

Hi Rob,

I've downloaded the 5.3 snapshot and re-run the test against it and it still 
has a duplicate message failure.

Snapshot was : apache-activemq-5.3-20080922.231550-14-bin.zip

Would you expect the fix to be included in this snapshot?

Cheers,
Johnny

> Duplicate message received when producing and consuming concurrently
> --------------------------------------------------------------------
>
>                 Key: AMQ-1936
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1936
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.1.0
>         Environment: Dell Precision with 2.13GHz dual core, 3.25 GB RAM 
> running on Windows XP SP2. Test is running on JDK1.5.0_12.
>            Reporter: Johnny
>            Assignee: Rob Davies
>             Fix For: 5.3.0
>
>         Attachments: activemq-duplicate-msg-check.xml, 
> ActiveMQDuplicateMessageTest.java, log4j.xml
>
>
> Hello,
> We are receiving duplicate messages when processing a moderate numbers of 
> messages ( ~60,000 ), I have attached a JUNIT test which re-produces the 
> issue on my machine with the broker configuration file used. Please note that 
> It does take a few minutes to generate the test failure.
> The test needs to be run with increased heap memory using the JMV option 
> -Xmx512m
> We initially found the issue using the IONA Fuse version 5.1.0.0 which would 
> produce the same issue at 30,000 messages and without persistence storage. I 
> later downloaded the ActiveMQ 5.1.0 version which would pass at 30,000 but 
> fail at 60,000.
> It is causing major issues for our project and hindering our application from 
> going to production.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to