:john.lil...@redpointglobal.com>
From: Justin Bertram
Sent: Friday, December 30, 2022 12:46 PM
To: users@activemq.apache.org
Subject: Re: Message Selectors vs multiple queues
*** [Caution] This email is from an external source. Please use caution
responding, opening attachments or clicking embedded links. ***
s
> John
>
>
> [image: rg] <https://www.redpointglobal.com/>
>
> John Lilley
>
> Data Management Chief Architect, Redpoint Global Inc.
>
> 888 Worcester Street, Suite 200 Wellesley, MA 02482
>
> *M: *+1 7209385761 <+1%207209385761> | john.lil...@redpoint
I'm not aware of any specific rule of thumb on the upper limit on the
number of queues. The broker itself has no arbitrary limit so it really
depends on your hardware, heap-size, use-case, performance goals, etc.
Justin
On Thu, Dec 22, 2022 at 6:36 AM Mark Johnson
wrote:
> Hi Justin,
>
> Is t
+1 7209385761 |
john.lil...@redpointglobal.com<mailto:john.lil...@redpointglobal.com>
-Original Message-
From: Mark Johnson mailto:spike.john...@gmail.com>>
Sent: Thursday, December 22, 2022 5:35 AM
To: users@activemq.apache.org<mailto:users@activemq.apache.org>
Subject: Re: Messa
Hi Justin,
Is there a rule of thumb for the limit of Y?
Just wondering about the realistic upper limit on the number of queues.
Thanks
On Wed, 21 Dec 2022 at 15:21, Justin Bertram wrote:
> Generally speaking I would avoid use-cases involving a JMS queue +
> selectors when possible for the fol
ertram
Sent: Wednesday, December 21, 2022 8:21 AM
To: users@activemq.apache.org
Subject: Re: Message Selectors vs multiple queues
*** [Caution] This email is from an external source. Please use caution
responding, opening attachments or clicking embedded links. ***
Generally speaking I would avo
Generally speaking I would avoid use-cases involving a JMS queue +
selectors when possible for the following reasons:
- The queue has to be scanned over and over for messages which match the
selectors. The deeper the queue gets the more scanning is required. This
adds up over time.
- A single qu
ent: Tuesday, December 20, 2022 9:54 PM
To: users@activemq.apache.org
Subject: Re: Message Selectors vs multiple queues
*** [Caution] This email is from an external source. Please use caution
responding, opening attachments or clicking embedded links. ***
I'd add my opinion from the maintenance
I'd add my opinion from the maintenance perspective.
We use both setups in our cloud service and when it comes to solving issues
it's a lot better to have separate queues, as you can pause these individually.
Selecting what not to consume on the consumer side can get very complicated.
Jan
Dne
+1,
I would love this feature too :)
Bye,
Norman
2010/9/23 Thomas Dudziak :
> The problem is that this only works if the message is due, so to
> speak. For systems where you have more than a few scheduled messages,
> you'll need something like a queue browser (which can actually see the
> whole
The problem is that this only works if the message is due, so to
speak. For systems where you have more than a few scheduled messages,
you'll need something like a queue browser (which can actually see the
whole queue, e.g. AMQ-2172) that allows you to select and delete
messages by message selector
Hi Tom,
note that scheduled messages are kept by the broker in a specialized
store, and will be sent to the queue/topic only when time comes. These
send messages have "scheduledJobId" property set, which you can use to
select them.
Cheers
--
Dejan Bosanac - http://twitter.com/dejanb
Open Source
On Tue, Sep 30, 2008 at 9:21 AM, James Strachan
<[EMAIL PROTECTED]> wrote:
> 2008/9/30 Bruce Snyder <[EMAIL PROTECTED]>:
>> On Tue, Sep 30, 2008 at 8:52 AM, my_forum <[EMAIL PROTECTED]> wrote:
>>
>>
>>> Thanks for your reply!
>>> After some investigation I found out that message selectors is not ac
2008/9/30 Bruce Snyder <[EMAIL PROTECTED]>:
> On Tue, Sep 30, 2008 at 8:52 AM, my_forum <[EMAIL PROTECTED]> wrote:
>
>
>> Thanks for your reply!
>> After some investigation I found out that message selectors is not actually
>> what I need.
>> I want to support dynamic number of priorities and worki
On Tue, Sep 30, 2008 at 8:52 AM, my_forum <[EMAIL PROTECTED]> wrote:
> Thanks for your reply!
> After some investigation I found out that message selectors is not actually
> what I need.
> I want to support dynamic number of priorities and working with selectors I
> will have to create "one bean
bsnyder wrote:
>
> On Mon, Sep 29, 2008 at 9:25 AM, my_forum <[EMAIL PROTECTED]> wrote:
>>
>> Guys,
>> could anyone give me an example of usage message selectors with Message
>> Driven beans?
>> I want to process my messages by priority so I think using selectors will
>> be
>> a correct choice.
2008/9/30 my_forum <[EMAIL PROTECTED]>:
>
>
> bsnyder wrote:
>>
>> On Mon, Sep 29, 2008 at 9:25 AM, my_forum <[EMAIL PROTECTED]> wrote:
>>>
>>> Guys,
>>> could anyone give me an example of usage message selectors with Message
>>> Driven beans?
>>> I want to process my messages by priority so I thin
On Mon, Sep 29, 2008 at 9:25 AM, my_forum <[EMAIL PROTECTED]> wrote:
>
> Guys,
> could anyone give me an example of usage message selectors with Message
> Driven beans?
> I want to process my messages by priority so I think using selectors will be
> a correct choice.
> Has somebody implemented mess
On 12/10/2007, Terry K <[EMAIL PROTECTED]> wrote:
>
> .. what worries me at this point is introducing yet anothrer level of
> software complexity to solve what is really a simple requirement. I can see
> a simple database table with a little SQL code could solve this problem.
> What advantage does
.. what worries me at this point is introducing yet anothrer level of
software complexity to solve what is really a simple requirement. I can see
a simple database table with a little SQL code could solve this problem.
What advantage does a JMS Queue (which is not a trivial software
infrastructure
On 11/10/2007, Terry K <[EMAIL PROTECTED]> wrote:
>
> ... thanks for the suggestions - message groups do sound like a plausible
> solution.
>
> I am not interested in assigning a group of messages to particular sessions
> indefinately as the groups will be small and many. Once the high priority
> m
... thanks for the suggestions - message groups do sound like a plausible
solution.
I am not interested in assigning a group of messages to particular sessions
indefinately as the groups will be small and many. Once the high priority
message has been dequeued with all related messages (at that po
On 10/10/2007, Terrk K <[EMAIL PROTECTED]> wrote:
>
> I cannot find enough documentation on message selectors but have many
> questions.
>
> Message selectors are more like fliters right? If so, what is the underlying
> selection policy of the broker? Age, priority, moon phases?
The selector descr
Sounds to me like "Message Groups" may be what you're looking for.
http://activemq.apache.org/message-groups.html
Joe
Terry K wrote:
>
> I cannot find enough documentation on message selectors but have many
> questions.
>
> Message selectors are more like fliters right? If so, what is the
24 matches
Mail list logo
