FAQ updated. Please review.
Regards,
Richard.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4242496#4242496
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4242496
___
jboss-user
Thanks Richard,
Now the FAQ has the latest AS 5 included. great stuff!
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4242502#4242502
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4242502
JBossMessaging has automatic failover.
If you want to control the failover the same style you would do on JBossMQ, you
need to disable failover and do the reconnects yourself.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4240914#4240914
Reply to the post :
Clebert,
Thanks for your input. I am fine to manually failover in my producer, as I
control that code.
However the problem I'm having is that, upon restarting a cluster node, the
MDBs do not 'wake up' and start consuming messages from the HA queue. The code
to connect the MDBs is controlled
gaohoward,
I would gladly rework and update the Wiki FAQ for you if you can furnish me
with a solution :)
Regards,
Richard.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4240921#4240921
Reply to the post :
gaohoward,
Awesome. You are a legend. Look forward to hearing how you go. If it helps:
1. I made the changes described in the Wiki, then copied the 'all' folder to a
new folder (I called it 'cluster2') and started a second instance of JBoss
using 'run -c cluster2
Howard,
Hmmm. From watching my logs, I think the reason the MDBs aren't 'waking up'
upon bouncing a node is because JBoss Messaging is still creating 3 local
queues, not one HA singleton one.
This, despite the fact that destinations-service.xml is under
deploy-hasingleton. Do I need to do
gaohoward wrote :
| Using /ClusteredConnectionFactory, each time you gets a connection, you
connects to a different node (round robin load balancing by default).
|
| By enable Message Suckers in the cluster, messages will be pulled off from
nodes that have no local consumers to the nodes
Tim,
Thanks for helping out.
If I understand correctly, JBM 1.x load-balances at distribution time, not
consumption time. In my case, I am sending 1000 messages to the queue in one
initial batch.
I see an initial flurry while all 3 of my consumers consume messages, then the
fastest one stops
Actually JBM 1.x does both. (BTW there is a FAQ on this, but I didn't right it
so can't vouch for it's accuracy).
When using a clustered connection factory, subsequent *connections* will
normally be created to different nodes of the cluster, by default in a round
robin fashion.
So connection
kennardconsulting wrote : Tim,
|
| What you say is very interesting. Could you please elaborate on what you
mean when you say:
|
| The local queue will first attempt to send messages to the local queue
| until it determines it is busy
|
| Do you mean the 'local queue will send
very informative thread i've seen in a while ! thanks every one !
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4240973#4240973
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4240973
Hi Richard,
The JBM is under deploy/messaging in AS 5.1 as you found.
For how to setup a HA-Singleton cluster, I suggest you post a question to the
AS forum, where you can get a better help on this.
Howard
View the original post :
Hi Richard, I'll take a look at the wiki. Thanks.
Howard
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4240925#4240925
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4240925
___
Tim,
What you say is very interesting. Could you please elaborate on what you mean
when you say:
The local queue will first attempt to send messages to the local queue
until it determines it is busy
Do you mean the 'local queue will send messages to the prefetch buffer'?
If the processing
Tim:
Brilliant. I tried setting PrefetchSize to 1 and the 3 nodes are now consuming
messages evenly. This also explains why I thought there were still 3 local
queues even though I had defined the queue in deploy-hasingleton: there were
not 3 local queues, just 3 prefetch buffers.
Thanks so
Thanks Richard for the effort. I'll check the FAQ.
Howard
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4241039#4241039
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4241039
___
Using /ClusteredConnectionFactory, each time you gets a connection, you
connects to a different node (round robin load balancing by default).
By enable Message Suckers in the cluster, messages will be pulled off from
nodes that have no local consumers to the nodes that have local consumers but
gaohoward,
Thanks as always for your help. I don't think what you suggest is going to work
because:
1. As soon as new messages get delivered to its local queue, it will stop
sucking from other nodes. This is fine but it will mess up the delivery order
of messages
2. If I turn on 'strict
gaohoward,
Please, please - I am begging you!
I have spent several days on this and one of the main problems is that in all
of the documentation and forum postings members of one team keep referring
people to another team, who refer people to another team etc.
I understand different people
20 matches
Mail list logo
