Hi James, I am using ActiveMQ 4.1.1.
I have two topic publishers and n number of durable subscribers as consumers. I have a network of two brokers each embedded inside jboss 4.0.3SP1 instances running behind a load balancer. The main issue I am facing is that when I restart my consumers, the old messages which were already delivered and acknowledged by the subscribers were redelivered. We are doing the following things at the publisher and subscriber end At the publisher end 1) We are setting the TTL to 1000 ms 2) Setting the expiration at message level to 1 Hr At the subscriber end 1) Its a Durable subscriber and always connects with the same clientID even after restarting. 2) Our subscriber Id and the client ID which we set in the connection are same. 3) After consuming every message, the subscriber do an ack and commit. When we test the durable subscriber in a setup without network of brokers, the older messages are not redelivered. Is that something to do with network of brokers. We are using failover transport at the subscriber end. Pls clarify Thanks Gnanaprakash James.Strachan wrote: > > Using what version & what kind of messaging? > > On 17/12/2007, Gnanaprakash <[EMAIL PROTECTED]> wrote: >> >> Hi, >> >> I am also facing a similar issue. >> >> The messages are not expiring as expected and they are consumed again by >> the >> subscribers >> if we bring them down and restart again. >> >> We are setting the expiration TTL on client side and setting the message >> expiration age too. >> >> Also in the durable subscriber we are doing an ack and commiting the >> message >> and subscriber. >> >> Still the message does not expire and when we restart the consumers, >> they >> are redelivered again. >> >> Has this been fixed or is there any other configuration we need to do. >> >> Thanks >> Gnanaprakash >> >> >> >> Suchitha Koneru (sukoneru) wrote: >> > >> > Hello Active MQ users/developers , >> > Our application uses non persistent >> > embedded broker ,durable subscribers , topic publishers . The active mq >> > version is 4.1.1(release version). There are two topic publishers and >> > two durable subscribers respectively. >> > In your previous responses, you specified that for durable subscribers >> > active mq maintains a queue of messages (Message Queue). For each of >> > the durable subscribers, a queue of references is maintained , the >> > references point to the messages stored in Message Queue. >> > Are these queues maintained in RAM or on the disk ? >> > There is TTL of 5 minutes on all the messages. >> > What is the behavior if the messages are not consumed after 5 minutes >> > ? There is JIRA issue AMQ-1112 (Messages still exist after TTL). >> Will >> > the messages keep accumulating in the message queue and the >> > corresponding references in the individual queues ? >> > >> > if this is the case will active mq occupy a lot of disk space.? >> > >> > The active mq data folder is always around (40.7-40.8 MB). >> > >> > This issue is fixed in 5.0 snap shot, cannot upgrade to snap shot >> > version, as Iam not sure how stable it is. We are going into production >> > next month. >> > >> > Please let me know, as to what can be done in this regard. Would >> > switching to non durable subscribers solve the problem ? >> > >> > is there a tool which I can use for browsing through active mq's >> > Message Queues ? >> > >> > thanks, >> > Suchitha. >> > >> > >> > >> > >> > >> > >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/active-mq-%28message-expiration%29-tp12247012s2354p14374029.html >> Sent from the ActiveMQ - User mailing list archive at Nabble.com. >> >> > > > -- > James > ------- > http://macstrac.blogspot.com/ > > Open Source Integration > http://open.iona.com > > -- View this message in context: http://www.nabble.com/active-mq-%28message-expiration%29-tp12247012s2354p14402135.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
