-
1. Re: Problem for Clustered JMS lookup.
gaohoward Jan 3, 2010 10:38 PM (in response to yongyao)Please read JBoss documentation on how to use HA JNDI.
JBM clustering doesn't need HA-JNDI to work. Just make sure you setup JBM cluster correctly as per the doc and get connections using a clustered connection factory. You still can use normal JNDI (1099 port) to get a clustered connection factory if you want.
Howard
-
2. Re: Problem for Clustered JMS lookup.
yongyao Jan 3, 2010 10:58 PM (in response to gaohoward)Hi, Howard,
Thanks a lot for your reply.
I also found 1099 can work, for example, I can set provider_url to 10.131.21.9:1099,10.131.21.10:1099. And when one node is down, the message can be handled by another. But the question is that it is not the real cluster, there is no load balance, because only one node can handle the message. And only if the master one is down, the another node can begin to handle the message. Did this means I made the wrong cluster configuration?
I used message-driven bean, But I didnot find any configuration in Jboss clustering guider for it. it only included the session bean...
For example, in the section -- 1.1.4. EJB Session Bean Clustering Quick Start, there is no clustered child element for message-driven bean, but only for session bean.
Regards
Yong
-
3. Re: Problem for Clustered JMS lookup.
yongyao Jan 4, 2010 1:49 AM (in response to yongyao)Hi, Howard,
You are right. I made the mistake that I didnot config the post office bean as clustered. After fixing it, it can work now.
Regards
Yong