2 Replies Latest reply on May 26, 2006 3:25 AM by dav dav

    Singleton, cluster, JMS PROBLEM!!!!!!!

    dav dav Newbie

      HI to all.
      i'm newbie of cluster an d jms , i read a documentation and i know that if i want to clustered two jboss with jms's application a need to configure it in singlketon righy ?
      i delete the all/jms
      and i create this tree directory:
      all\deploy\deploy-hasingleton\jms

      i leave the defoult ds for hypersonic in /all

      when i started the 1 jboss is all ok

      when i started teh second i have this error:

      13:53:49,547 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
      MBeans waiting for other MBeans:
      ObjectName: jboss.mq.destination:service=Queue,name=cis/httpserver
       state: CONFIGURED
       I Depend On: jboss.mq:service=DestinationManager
      
       Depends On Me:
      ObjectName: jboss.mq.destination:service=Queue,name=cis/httpClient
       state: CONFIGURED
       I Depend On: jboss.mq:service=DestinationManager
      
       Depends On Me:
      
      MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM:
      ObjectName: jboss.mq:service=DestinationManager
       state: NOTYETINSTALLED
       I Depend On:
       Depends On Me: jboss.mq.destination:service=Queue,name=cis/httpserver
       jboss.mq.destination:service=Queue,name=cis/httpClient
      
      


      if is necessary i paste the deployment descriptor..
      please answered soon is a lot of time that i have thi sproblem and i never solved.


        • 1. Re: Singleton, cluster, JMS PROBLEM!!!!!!!
          Stéphane Nicoll Newbie

          You don't need to remove the deploy/jms directory. Please restart from a clean/fresh "all" server.

          The deploy-hasingleton is used to deploy services on only one node. This needs to be identical on all nodes in your cluster so configure it first on one node and then copy paste it in all other nodes of your cluster.

          The deploy/jms is only used to allow JMS access from other nodes. Keep it like this.

          If you need to configure queues, do so in the deploy-hasingleton directory.

          I think the error you have is because you're trying to deploy the JMS destinations (queues/topics) on all nodes. You only need to do so on the node running the JMS server.

          HTH,
          Stéphane

          • 2. Re: Singleton, cluster, JMS PROBLEM!!!!!!!
            dav dav Newbie

            Many thanks....

            I think that you are in right way... but how to for make this configuration in my deployer configuration file?
            i have an'application-service.xml where i put all my destination META-INF directory and not in deploy-hasingletone/jms

            <server>
            
             <mbean code="org.jboss.mq.server.jmx.Queue"
             name="jboss.mq.destination:service=Queue,name=cis/httpserver">
             <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
             </mbean>
             <mbean code="org.jboss.mq.server.jmx.Queue"
             name="jboss.mq.destination:service=Queue,name=cis/httpClient">
             <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
             </mbean>
             <mbean code="net.sf.hibernate.jmx.HibernateService" name="jboss.jca:service=HibernateFactory,name=HibernateFactory">
             <depends>jboss.jca:service=RARDeployer</depends>
             <depends>jboss.jca:service=LocalTxCM,name=DefaultDS</depends>
             <!-- Make it deploy ONLY after DataSource had been started -->
             <attribute name="MapResources">mappings/CisConfig.hbm.xml</attribute>
             <attribute name="TransactionManagerLookupStrategy">net.sf.hibernate.transaction.JBossTransactionManagerLookup</attribute>
            
             </mbean>
             <mbean code="xqueue.config.ConfigManagerService" name="cis.config:service=ConfigManager">
             <attribute name="JndiName">cis/config/ConfigManager</attribute>
             <depends>jboss:service=Naming</depends>
             </mbean>
            
            
            
            </server>