-
1. Re: Alternative to Topic with many subscribers (100 +) ? (stalling delivery)
ataylor May 10, 2010 4:51 AM (in response to tpaterson0512)however - it seems that we could easily get into a situation where one or more subscribers stops consuming, due to network issues, etc,
and eventually the other subscribers would no longer be able to consume any new messages,
since all of the messages in memory for that Address would be the messages which are only to be consumed by the problem consumers.
This would only be a problem if the subscribers were durable, is this the case?
we could of course - change to using lots of Queues and avoid the problem above,
but that would presumably mean we would use 100 times as much memory and disk space,
since each message would be copied to each of the 100 queues ?
Actually there is no difference, a subscription is represented by a queue any way and also the same message will only be persisted once. And only a reference is held in the queue.
-
2. Re: Alternative to Topic with many subscribers (100 +) ? (stalling delivery)
timfox May 10, 2010 6:53 AM (in response to ataylor)It's not mentioned in this thread, but I guess the user is using paging for this to occur.
If so, there is already a JIRA for this.
-
3. Re: Alternative to Topic with many subscribers (100 +) ? (stalling delivery)
tpaterson0512 May 10, 2010 7:44 AM (in response to timfox)Hi Guys,
Yes - the messages are durable,
and we are also using paging