activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pieter (JIRA)" <>
Subject [jira] Commented: (AMQ-1389) Duplicate messages with durable subscribers and perstitent messages
Date Mon, 01 Oct 2007 11:17:23 GMT


Pieter commented on AMQ-1389:

I think I've traced the source of the problem: it only appears when I have this persistenceAdapter

          <journaledJDBC journalLogFiles="5" dataDirectory="${activemq.base}/activemq-data"/>

> Duplicate messages with durable subscribers and perstitent messages
> -------------------------------------------------------------------
>                 Key: AMQ-1389
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.0.0
>         Environment: linux, persistent="true" in broker config
>            Reporter: Pieter
> I have two consumers, having a durable subscription on a topic. If I send a persistent
message to the topic, everything works ok. However, when I restart the consumers, one of them
receives the message again after connecting (it seems to be the one that ACK's the message
as second). Reconnecting again doesn't give any problems, the messages aren't redelivered.
> This problem does not happen when only a single consumer is connected. Also, it doesn't
appear if the persistent message is sent before the consumers are connected.
> Steps to reproduce:
> Start two consumers with a durable topic subscription (in the example/ directory):
> $ ant consumer -Ddurable=true -DclientId=test1 -Dtopic=true
> $ ant consumer -Ddurable=true -DclientId=test2 -Dtopic=true
> Send persistent messages to this topic:
> $ ant producer -Ddurable=true -Dtopic=true
> Kill consumers and start them again. One of them willl receive each message again.
> This also happens if I use the STOMP protocol. In ActiveMQ 4.1.1 things work as expected,
but in snapshots (I tried 4.2 and 5.0), the behaviour is as above.

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

View raw message