Actually, ixnay the cache config stuff, I don't think it needs to be there
since its a master/slave setup...
Or am I wrong (anyone?)
|
| DefaultJMSProvider
|
| org.jboss.jms.jndi.JNDIProviderAdapter
|
|
| XAConnectionFactory
|
| XAConne
sorry, I should have been more explicit, as the wiki post is lacking.
In your jms-ds.xml, look for the JMSProviderLoader mbean. It's entry should be
changed to look something like this:
|
| DefaultJMSProvider
|
| org.jboss.jms.jndi.JNDIProviderAdapter
|
|
Gents,
You'll want to change your MDBs to look in the global jndi tree for the JMS
Queue/Topic it is trying to bind to. See this wiki entry:
http://wiki.jboss.org/wiki/HowToConfigureMDBsToSubscribeToATopic
Basically, since the JMS Server (Jbossmq) is a cluster singleton and so are its
destina
"jaikiran" wrote :
| Then i started another node in the cluster and the EAR was picked up by the
farm service. When the MDB was being deployed, the queue was not created again
because the node found it already existing in the cluster:
|
what if I want it to be created on the second node. I
I just tried a similar thing on my setups. I created a MDB pointing to a
non-existent queue (queue/ABC) and placed that EAR file in the farm folder of
"all".
@MessageDriven(activationConfig =
| {
| @ActivationConfigProperty(propertyName="destinationType",
| propertyValue="javax.jms.Queue"),
thanks, you still can remember my last post :) . The first in cluster will get:
2008-08-22 12:13:06,152 WARN [org.jboss.ejb3.mdb.MessagingContainer]
destination not found: queue/XXX/YYY reason:
javax.naming.NameNotFoundException: queue/XXX/YYY
| 2008-08-22 12:13:06,152 WARN [org.jboss.ejb3.m
"gan.gary" wrote :
|
| but when runnning in "all" configuration, the MDB only can be created by
first Jboss (let say: 10.10.10.10) in network, the subsequent running JBoss
instance ((let say: 10.10.10.11, 10.10.10.12) detected the running instance,
seems clustering it automatically, cause
from the server.log, I can tell the second(or following running JBoss instance)
in the network is clustered:
INFO [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] Number
of cluster members: 2
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=417
