>
> > Putting in a hardcoded drop the message if non-persistent and wait if
> > persistent should not be bad..
> > The hard coded case will help clear up how we need to reorganize things
>so
> > that we can make that logic plugable.
>
>I don't understand this though... why hardcoded anything... p
> >How about a pluggable that could implement an adaptive algorithm, such that
> >we can let applications determine the trade offs. Something simple like a
> >min/max for starts, such that messages are absorbed by ClientConsumers
> >until
> >max, then once min has reached we refill. Or a move ad
> Hi, just a sidenote: deploying two MDB ataching to the same destination
> has unspecifyed behaviour if a remember the EJB 2.0 spec correct - so we
> are spec compliant ;-)
The specs (EJB + JMS) are broken, in more ways than one.
Lack of specification in this area is good and bad. Good because
Lets build a test case for it
Regards,
Hiram
>From: [EMAIL PROTECTED]
>Reply-To: [EMAIL PROTECTED]
>To: [EMAIL PROTECTED]
>Subject: Re: [JBoss-dev] persistent messages with more than one consumer
>Date: Thu, 9 Aug 2001 16:35:54 +0200 (CEST)
>
>Hi, just a sidenote: deplo
Hi, just a sidenote: deploying two MDB ataching to the same destination
has unspecifyed behaviour if a remember the EJB 2.0 spec correct - so we
are spec compliant ;-)
But it would be really good if this could be fixed.
If I remember correct we also have a problem with durable topics. I.e
deplo
> > 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 t
> 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 th
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 m
