[Messaging, JMS & JBossMQ] - Clustered MDB and Fault Tolerance
by tnine
Hello all,
I'm trying to configure my MDB's to run in an HA environment. I have half of the MDB working. The mdb performs the following tasks
1. Read from HA JBoss MQ Queue
2. Process message
3. Push the message onto a different queue.
I'm using 2 identical nodes (vmware instances, prodjboss1, and prodjboss2), and I have edited the file 'deploy/jms/hajndi-jms-ds.xml' to have the following
prodjboss1
| java.naming.provider.url=${jboss.bind.address:localhost}:1100,prodjboss2:1100
|
prodjboss2
| java.naming.provider.url=${jboss.bind.address:localhost}:1100,prodjboss1:1100
|
Both my MDB's read from the correct master node. However, I'm trying to connect to a different output queue via my MDB, and I'm not getting the expected behavior. I'm using the following JNDI properties on both nodes when attempting to connect to the output queue
| java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
| java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
| java.naming.provider.url=jnp://prodjboss1:1100,prodjboss1:1100
|
The lookup always works correctly on the node that's the master node, but fails on all slave nodes. Am I missing another property that I need to add in order to get automatic master discovery working and get all slaves connecting to the master MQ node to push data onto the queue?
Thanks,
Todd
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081479#4081479
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4081479
18 years, 7 months
[JBoss Seam] - Re: communicating between two seam applications
by norman.richards＠jboss.com
There really isn't a standard way to share classloaders between applications. For remote beans, you need the interfaces from app2 in app1 and the interfaces from app1 in app2. I don't know what other app servers offer to provide the equivalent of a shared-named repository.
If you are sharing classloaders, there's really no reason not to use one big ear instead. If you hot deploy app1 you nearly always need to hot deploy app2 also to avoid classloader issues. Why not bundle in one big ear and force yourself to do the right thing on redeploy? The alternative, in jboss, is to extract common classes to a third app. app1 and app2 can be safely separately redeployed. If the common classes change then both app1 and app2 should be redeployed.
No, we don't really have a link to JMX MBeans. You probably don't want direct app to mbean communication for the most part. Generally you want your MBeans to manage services that are exposed through JNDI or some other communications mechanism. In either case @Factory and @Unwrap are probably your best bets for exposing these services to Seam.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081474#4081474
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4081474
18 years, 7 months