activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Komandur <sridharkoman...@komandur.com>
Subject Re: [jira] Commented: (AMQ-850) add the ability to timeout a consumer to
Date Wed, 09 Aug 2006 19:25:53 GMT


Thanks for the reply James.

Reading  AMQ-855 and this thread, it seemed like messages were stuck  in
prefetch buffers 
when the associated consumer behaved.

Would you mind  some clarification to confirm what I am suggesting is what
is happening  :-)

1 When are the messages actually moved to prefetch buffer upto its limit ? 
By "moved" I mean that it is not available to be dispatched to another
active consumer.

The 'prefetch' had the connotation of preallocating 'yet to be sent'
messages to a consumer.

2 *Assuming* a message is put in prefetch buffer associated with a consumer
*after* it is sent: is there a notion of message expiry (based on either
time or misbehaving client detection) and returning the message to a central
pool from which they can be sent to other active consumers ?

Thanks
Regards
- Sridhar


-- 
View this message in context: http://www.nabble.com/-jira--Created%3A-%28AMQ-850%29-add-the-ability-to-timeout-a-prefetch-buffer-to-prevent-a-single-consumer-grabbing-messages-tf2014900.html#a5732254
Sent from the ActiveMQ - Dev forum at Nabble.com.


Mime
View raw message