setting up cluster on JBoss 4.2.0 GA (messaging conflict)

[navjeetc]

I am setting up the cluster of two nodes on windows XP but having problems starting up even a single node. I have taken the base server/all configuration as the starting point and adding on my application specific configuration to it. I have also added JBoss messaging (1.2.0 GA) to it (instead of using default jms which lacks clustering support). Now that seems to conflicts with jms which is installed with all configuration that seems to be used for clustering (not sure). Currently I am getting the following error:


--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.messaging:service=PersistenceManager
State: NOTYETINSTALLED
Depends On Me:
jboss.messaging:service=ServerPeer


Seems like this may be because there is a PersistenceManager defined in JBoss messaging and also in deploy-hasingleton/jms that comes with server/all config. So my question is What, if it all can I strip off from messaging components/services in server/all configuration so that it does not conflict with JBoss messaging or is it just a matter of changing the service names like PersistenceManager in this case?

[navjeetc]

Some more information on the error. I am not sure if it is service name conflict issue as I mentioned in my previous message. The whole error is:

09:47:56,908 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

--- MBeans waiting for other MBeans ---
ObjectName: jboss.messaging.connectionfactory:service=ConnectionFactory
 State: CONFIGURED
 I Depend On:
 jboss.messaging:service=ServerPeer
 jboss.messaging:service=Connector,transport=bisocket
 jboss.messaging:service=PostOffice

ObjectName: jboss.messaging.connectionfactory:service=NonClusteredConnectionFa
ory
 State: CONFIGURED
 I Depend On:
 jboss.messaging:service=ServerPeer
 jboss.messaging:service=Connector,transport=bisocket
 jboss.messaging:service=PostOffice

ObjectName: jboss.messaging:service=ServerPeer
 State: CONFIGURED
 I Depend On:
 jboss.messaging:service=PersistenceManager
 jboss.messaging:service=JMSUserManager
 jboss.messaging:service=Connector,transport=bisocket
 Depends On Me:
 jboss.messaging.connectionfactory:service=ConnectionFactory
 jboss.messaging.connectionfactory:service=NonClusteredConnectionFactory
 jboss.messaging:service=Bootstrap
 jboss.jca:service=ManagedConnectionFactory,name=JmsXA

ObjectName: jboss.messaging:service=Bootstrap
 State: CONFIGURED
 I Depend On:
 jboss.messaging:service=ServerPeer

ObjectName: jboss.jca:service=TxCM,name=JmsXA
 State: CONFIGURED
 I Depend On:
 jboss.jca:service=ManagedConnectionPool,name=JmsXA
 jboss.jca:service=CachedConnectionManager
 jboss.security:service=JaasSecurityManager
 jboss:service=TransactionManager
 Depends On Me:
 jboss.jca:service=ConnectionFactoryBinding,name=JmsXA

ObjectName: jboss.jca:service=ManagedConnectionPool,name=JmsXA
 State: CONFIGURED
 I Depend On:
 jboss.jca:service=ManagedConnectionFactory,name=JmsXA
 Depends On Me:
 jboss.jca:service=TxCM,name=JmsXA

ObjectName: jboss.jca:service=ManagedConnectionFactory,name=JmsXA
 State: CONFIGURED
 I Depend On:
 jboss.messaging:service=ServerPeer
 jboss.jca:service=RARDeployment,name='jms-ra.rar'
 Depends On Me:
 jboss.jca:service=ManagedConnectionPool,name=JmsXA

ObjectName: jboss.jca:service=ConnectionFactoryBinding,name=JmsXA
 State: CONFIGURED
 I Depend On:
 jboss.jca:service=TxCM,name=JmsXA

--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.messaging:service=PersistenceManager
 State: NOTYETINSTALLED
 Depends On Me:
 jboss.messaging:service=ServerPeer

[brian.stansberry]

If you are deploying JBM, you should remove the old JBoss MQ install unless you have a specific reason for keeping it. I believe (not positive) that JBM has install scripts to help you do that.

That said, I doubt your problem is a service name conflict. Your message is for jboss.messaging:service=PersistenceManager. The JBossMQ service is jboss.mq:service=PersistenceManager.

Suggest you post on the Messaging forums where the folks more familiar with the details of the messaging installation live.