yes...
When Message are placed on the JMSQueue object, they get placed on a list
until we have a consumer that will accept the message. The deal is that
with an async consumer (like a MDB), when he subscribes to the destination,
we just 'turn on the message valve' allowing messages to flow to the
consumer as they come into the JMSQueue object. The problem is that the
ClientConsumer object queues up messages destined for the client (because
the Destination does not want to wait for a message to be transmited). So
if you place 1000 message on a queue, they will be waiting in the JMSObject.
Then when you start the MDB, those messages will be moved over to the
queue on ClientConsumer associated with the MDB (messages will wait there
until they are all transmited). It seems like we need to set a limit on how
big that client-bound message queue can get.
Right here is were we can make a whole bunch of desicions and how to try to
handle the speed vs robustness issues. If all ClientConsumer queues are
backed up should we wait till they have space or should be drop the message
if it is non-persistent? I say make it configurable. What other ways could
we handel this?
Regards,
Hiram
>From: Jason Dillon <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: <[EMAIL PROTECTED]>
>CC: <[EMAIL PROTECTED]>
>Subject: [JBoss-dev] persistent messages with more than one consumer
>Date: Wed, 8 Aug 2001 19:40:07 -0700 (PDT)
>
>I setup a client which sent 1k persistent messages to a queue, with no
>consumers attached. Then started up one consumer (MDB), which started to
>consume messages as it should. I then started up a second (also a MDB)
>which attached and then just sat there, even though there are still
>hundreds
>of messages to consume.
>
>I then sent another 10 messages to the queue and the second consumer woke
>up
>to process some of the 10 (not sure how many it actually did), then became
>idle once those messages were processed.
>
>I ran this test, because before I noticed that if I ran this test the first
>consumer would just sit there, which seems to have been fixed.
>
>Any ideas on why the second consumer would not see any of the messages from
>the first round?
>
>--jason
>
>
>_______________________________________________
>Jboss-development mailing list
>[EMAIL PROTECTED]
>http://lists.sourceforge.net/lists/listinfo/jboss-development
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
