You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Dejan Bosanac (JIRA)" <ji...@apache.org> on 2009/12/11 17:05:52 UTC

[jira] Resolved: (AMQ-2518) QueueBrowser cause duplicate message delivery on network broker after restart

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

Dejan Bosanac resolved AMQ-2518.
--------------------------------

       Resolution: Duplicate
    Fix Version/s: 5.4.0
                   5.3.1

Fixed with https://issues.apache.org/activemq/browse/AMQ-2519

> QueueBrowser cause duplicate message delivery on network broker after restart
> -----------------------------------------------------------------------------
>
>                 Key: AMQ-2518
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2518
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.3.0
>         Environment: Linux - Java 1.6
> Activemq 5.3.0
> JDBC Adapter Oracle 10G
>            Reporter: Giampaolo Tranchida
>            Priority: Critical
>             Fix For: 5.3.1, 5.4.0
>
>
>  I find a strange critical bug using QueueBrowser in an application and same issue using HermesJMS.
> 2 brokers in a network broker configured with static uri
> Starting with clean oracle DB ACTIVEMQ_MSGS for broker 1 and broker 2
> 1) I send 10 messages in queue A on broker 1
> 2) checking the broker 1 DB, I find 10 rows and 0 rows on broker 2 DB -> OK
> 3) I try to browse a first time the queue A on broker2 that return an empty list -> OK
> 4) I try to browse 5 times the queue A on broker2 that finally return my 10 messages -> KO
> 5) cheking the broker 1 DB, still 10 rows and 41 rows on broker 2 DB -> KO
> 6) I consume messages from broker 2 that return 10 messages
> 7) checking the broker 1 DB return 0 rows and still 41 rows on DB broker 2 -> KO
> 8) I restart the broker 2
> 9) I try to consume messages from broker 2 and I receive again my 10 messages -> critical !!!!
> 10 ) I restart again the broker 2 and I can consume again 10 messages, etc... until broker2 DB is empty.
> I try to add dynamicOnly="true" and/or conduitSubscriptions="false" but I have always the same problem.

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