You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Stefan Arentz <st...@gmail.com> on 2007/08/18 18:23:57 UTC
Message expiration on but queue only growing?
I have a queue that contains messages with an expiration time of 60
seconds. However I only see this queue growing. It is currently 30K
messages. I do see some decreases in size on JMX console graphs but
nothing that comes close to expiring messages that are now days old.
What could be the cause of that?
When I look in log files of consumers I see that expiration is enabled:
ActiveMQObjectMessage { ... expiration = 1187454102768, timestamp =
1187454042768 ... }
But it does not seem to actually work.
Has anyone seen this before?
S.
Re: Message expiration on but queue only growing?
Posted by James Strachan <ja...@gmail.com>.
Sure :-). Otherwise patches are always welcome
On 8/20/07, Stefan Arentz <st...@gmail.com> wrote:
> What would it take to get this in AMQ? Is this something you guys
> could do if it were a sponsored task?
>
> On 8/20/07, Rob Davies <ra...@gmail.com> wrote:
> > we dont actively try and purge messages from storage yet - only when
> > they are paged in from store to process (e.g. if there is a consumer
> > already).
> > This is a known issue: https://issues.apache.org/activemq/browse/
> > AMQ-1112
> >
> >
> > cheers,
> >
> > Rob
> >
> > 'Go Get Integrated - ride the Camel! - http://activemq.apache.org/
> > camel/'
> > http://rajdavies.blogspot.com/
> >
> >
> >
> > On Aug 18, 2007, at 5:23 PM, Stefan Arentz wrote:
> >
> > > I have a queue that contains messages with an expiration time of 60
> > > seconds. However I only see this queue growing. It is currently 30K
> > > messages. I do see some decreases in size on JMX console graphs but
> > > nothing that comes close to expiring messages that are now days old.
> > > What could be the cause of that?
> > >
> > > When I look in log files of consumers I see that expiration is
> > > enabled:
> > >
> > > ActiveMQObjectMessage { ... expiration = 1187454102768, timestamp =
> > > 1187454042768 ... }
> > >
> > > But it does not seem to actually work.
> > >
> > > Has anyone seen this before?
> > >
> > > S.
> >
> >
>
--
James
-------
http://macstrac.blogspot.com/
Re: Message expiration on but queue only growing?
Posted by Stefan Arentz <st...@gmail.com>.
What would it take to get this in AMQ? Is this something you guys
could do if it were a sponsored task?
On 8/20/07, Rob Davies <ra...@gmail.com> wrote:
> we dont actively try and purge messages from storage yet - only when
> they are paged in from store to process (e.g. if there is a consumer
> already).
> This is a known issue: https://issues.apache.org/activemq/browse/
> AMQ-1112
>
>
> cheers,
>
> Rob
>
> 'Go Get Integrated - ride the Camel! - http://activemq.apache.org/
> camel/'
> http://rajdavies.blogspot.com/
>
>
>
> On Aug 18, 2007, at 5:23 PM, Stefan Arentz wrote:
>
> > I have a queue that contains messages with an expiration time of 60
> > seconds. However I only see this queue growing. It is currently 30K
> > messages. I do see some decreases in size on JMX console graphs but
> > nothing that comes close to expiring messages that are now days old.
> > What could be the cause of that?
> >
> > When I look in log files of consumers I see that expiration is
> > enabled:
> >
> > ActiveMQObjectMessage { ... expiration = 1187454102768, timestamp =
> > 1187454042768 ... }
> >
> > But it does not seem to actually work.
> >
> > Has anyone seen this before?
> >
> > S.
>
>
Re: Message expiration on but queue only growing?
Posted by Rob Davies <ra...@gmail.com>.
we dont actively try and purge messages from storage yet - only when
they are paged in from store to process (e.g. if there is a consumer
already).
This is a known issue: https://issues.apache.org/activemq/browse/
AMQ-1112
cheers,
Rob
'Go Get Integrated - ride the Camel! - http://activemq.apache.org/
camel/'
http://rajdavies.blogspot.com/
On Aug 18, 2007, at 5:23 PM, Stefan Arentz wrote:
> I have a queue that contains messages with an expiration time of 60
> seconds. However I only see this queue growing. It is currently 30K
> messages. I do see some decreases in size on JMX console graphs but
> nothing that comes close to expiring messages that are now days old.
> What could be the cause of that?
>
> When I look in log files of consumers I see that expiration is
> enabled:
>
> ActiveMQObjectMessage { ... expiration = 1187454102768, timestamp =
> 1187454042768 ... }
>
> But it does not seem to actually work.
>
> Has anyone seen this before?
>
> S.