We will try the Durable subscribers with selector solution on our product- and
i will stress our application with both JBossMQ JBossMessaging.
I'll give you a feedback asap
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3974852#3974852
Reply to the post :
Omerlin-
I'm still trying to understand why you are using multiple selectors on a queue
- as already mentioned this is usually an antipattern (poor design) - there is
one case where it is not, so if you could explain to me more details about
how/what/why you use these selectors then I can
http://jira.jboss.org/jira/browse/JBMESSAGING-558
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3974305#3974305
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3974305
___
Thank you for your interrest !
Messages sent by the client to the shared Queue are group by a hash code.
The message unique identifier is named MSISDN.
For example, each message with attribute MSISDN (a long) finishing by 0 will be
carried to the sequencer 0
each message with attribute MSISDN
Perhaps you can send to a topic rather than a queue?
Each sequencer creates a (durable?) subscription with the selector you
mentioned?
If a message only ever matches the selector of one of the sequencers then this
should work for you.
Selectors on topic subscriptions are much more performant
We did not use topics because there is only one destination but if i
understand, even if you have only one destination (one topic) it's much more
better to use selector on topics than on queues.
So in our case we can imagine to have many consumers on the same topic with
different selector
Is
Yes.
When you create a consumer on a topic, it creates what is called a
subscription, this can either be durable or non durable (non durable survives
a failure like a jms queue).
Each subscription is basically a queue itself, but the difference from a jms
queue is that if you create the
I see a Sun article
http://developers.sun.com/sw/docs/articles/integration/tuning_tradeoffs.html
where they say the same thing :
Selectors are more performant on non durable subscribers
But the real performance gain would be to have many destination ... right ?
View the original post :
The most performant solution would be to have one topic and multiple
subscriptions - one subscription per selector.
I can see no performance gain in having multiple topics, and having multiple
queues will give you worst performance.
View the original post :
Having multiple consumers with selectors on a queue is normally an anti-pattern
(http://jira.jboss.com/jira/browse/JBAS-1348), and will always have poor
performance compare to using selectors with topics.
This will be true for any JMS implementation.
However I am surprised there is such a
I'm using the 1.0.1CR4.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3973915#3973915
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3973915
___
jboss-user mailing list
What is the difference in performance?
I am interested in replicating this locally, could you please describe your
experiment in such a way it can be replicated?
A working test would be best, if you have the time ...
View the original post :
12 matches
Mail list logo
