This content has been marked as final.
Show 2 replies
-
1. Re: setting up cluster on JBoss 4.2.0 GA (messaging conflict
navjeetc Jun 6, 2007 10:27 AM (in response to 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
-
2. Re: setting up cluster on JBoss 4.2.0 GA (messaging conflict
brian.stansberry Jun 6, 2007 10:57 AM (in response to navjeetc)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.