On Wed, 8 Feb 2006, Gilad Ben-Yossef wrote: > [EMAIL PROTECTED] wrote: > > Hi there, > > > > Having a message queue designed so that each queue (message type) is > > assigned > > to one process for reading. How do you handle a situation where the reading > > process of a given queue doesn't function and messages still arrive to that > > queue? > > 1. Will the queue fill up untill blocking the entire resource? > > 2. Can the blocking issue effect other message queues supposebly used by > > other > > applications? > > 3. Can you identify from a different process that there is a queue filling > > up? > > 4. Can you clear the overflown queue? > > > > Which message queue implementation - POSIX mq, Sys V mailboxes, > something you wrote? > > But the simplest answer is to not use the same queue for multiple > readers - use different message queues.
it won't help with sys V message queues - they have a system-wide limit on number of pending mesasges, in all sys V message queues (that, at least, used to be the case a few years ago - and i don't think it was changed). if anyone is using sys V message queues, they should scrap them ;) -- guy "For world domination - press 1, or dial 0, and please hold, for the creator." -- nob o. dy ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
