"chip_schoch" wrote : Thank you Andy and Clebert for taking the time to explain
this in detail. To reiterate, what you are saying is that if I need to have
multiple consumers processing messages from a clustered queue in FIFO order,
than I should have all my client consumers connect to the same
"chip_schoch" wrote :
| I assume this means the MessageSucker will be pulling message from the
nodes that have no consumers, to the node that has consumers.
|
Yep... exactly!
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4145626#4145626
Reply to the po
Thank you Andy and Clebert for taking the time to explain this in detail. To
reiterate, what you are saying is that if I need to have multiple consumers
processing messages from a clustered queue in FIFO order, than I should have
all my client consumers connect to the same node in the cluster.
Andy wrote : So in answer to your question, you would need to use a singleton
queue that all your consumers used and use the other node as a backup for fail
over.
A Singleton Queue it the way JBossMQ decided to implement cluster, and that was
as performant as having a single node.
If you need
anonymous wrote : I certainly appreciate your taking the time to participate in
this discussion. no problems.
In Jboss Messaging if a single queue has more than one Consumer, we will
deliver to the first available. If multiple consumers are registered with the
queue(with no message selectors) t
I certainly appreciate your taking the time to participate in this discussion.
It seems we have a permanent miscommunication. I am aware that setting
DefaultPreserveOrdering will preserve the ordering of the message consumption
but after numerous tests, some of which the results are posted in
As clebert mentioned earlier, setting DefaultPreserveOrdering on serverpeer
will assure message ordering.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4145065#4145065
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4145
>From 4.4.10.1 JMS 1.1 Spec
anonymous wrote : JMS defines that messages sent by a session to a destination
must be received
| in the order in which they were sent (see Section 4.4.10.2 âÂÂOrder of
Message
| Sends,â for a few qualifications). This defines a partial ordering
constraint
anonymous wrote : The idea of a queue having only one process that can pull
messages off is absurd
For every message a consumer receives from a queue it needs to send an ack back
to the server.
If a queue has a single consumer then the server can deliver many messages to
it which the consumer c
anonymous wrote : I am assuming that by receiver you mean consumer,
yes i do, too many trains of thought, i can't multtask :)
anonymous wrote : The whole point of using queues in a load balanced
environment is so that you can have a single work queue (or virtual single
queue as in a clustered que
anonymous wrote : Remember using queues is point to point so you should only
have one receiver.
I am assuming that by receiver you mean consumer, in JMS parlance. If that is
the case I don't know how you can make this assertion. The whole point of
using queues in a load balanced environment i
anonymous wrote : But why is Listener_2 getting the messages and not
Listener_1? I verified that the messages were put on appserver1 by stopping
before creating the consumers and using the jmx-console to see the message
count. I also verified that after creating the consumers each appserver had
I hate to belabor the point but it seems you are not quite understanding what I
am after. Let me try again.
Here is what I see.
My producer is connected to appserver1. Here is the serverLocatorURI from the
factory via the debugger:
bisocket://172.17.20.60:4457/?clientLeasePeriod=1&client
Just enable ordering, and it will work for you.
We just try to avoid unnecessary round trips to the cluster, and if you need to
guarantee ordering, we do things in a different way. That's all.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144650#4144650
Rep
I certainly appreciate your trying to keep me happy, as that is the prime
objective. Perhaps you could speak to my wife about that. And in all
seriousness, I do appreciate the time you have spent.
Requiring the producer of the messages to be cognizant of how many nodes are in
the cluster in o
Just a FYI (to keep you happy) I have invested a lot of time on this issue now
:-)
Load balancing on the ClusteredConnectionFactory, only guarantees that each
cf.createConnection() will point to a different Server. Having said that, a
MessageProducer will aways be bound to where its Connection
Let me clear up some things. First, I am not using 1.3.0. I am using JBoss AS
4.2.2.ga, JBM1.4.0.SP1, as stated in the intial post. I simply made the
mistake of referencing a paragraph in the 1.3 documentation. My bad.
I have been running numerous tests using the program I included, although
Ahhh... *Chapter* 3.1!
First of all.. don't use 1.3.0.. you will find several bugs that we have
fixed... including the documentation.
Second... you have FIFO on the cluster, but we aways distribute messages to
the local queue first.
Say, you have a ClusteredQueue deployed in two servers. When
That was Chapter 3.1 and Chapter 1.2.2 respectively. Here is the link
http://www.jboss.org/file-access/default/members/jbossmessaging/freezone/docs/userguide-1.3.0.GA/html/c_overview.html
It looks like it was the 1.3 UserGuide. I did initially set this stuff up last
year. It is only now that
"chip_schoch" wrote : By the way.
|
| From the JBoss Messaging Documentation 3.1
|
|
There is no such thing as JBoss Messaging Documentation 3.1. Maybe you are from
the future? :-) (eh eh... just kidding!)
I believe you are confusing JBossMQ with JBossMessaging docs.
The only docs
take a look at the DistributedQueueExample.
The load balancing is done by the clustered connection factory, on
createConnection(..) it will return a connection to one of the nodes in the
cluster in a round robin fashion. From then on all messages are routed through
this node. You dont need to u
By the way.
>From the JBoss Messaging Documentation 3.1
anonymous wrote : A JMS client uses HA JNDI to lookup the connection factory.
When creating connections using that connection factory a client side load
balancing policy will automatically chose a node to connect to.
>From the Clustering
Clearly I have been having some serious misunderstandings on how this works.
1. My clients use the JCA adapter because we develop on windows machines that
can run a windows only conversion library, so the "ConversionJMSProvider" is
defined to connect to localhost on our machines and to connect
JCA is to be used internally on the application server.
If you have external clients, why do you need the JCA adapter, why you can't
just use ClusteredXAConnectionFactory from the client side?
anonymous wrote :
java.naming.provider.url=jnp://devapp2.qa.cin.int:1100,jnp://devapp1.qa.cin.
24 matches
Mail list logo
