3 Replies Latest reply on Nov 4, 2011 6:53 PM by abhijith_p

    Problem setting up JMS on local cluster

    abhijith_p

      Hi all,

       

      I am trying to stand up JMS as a HASingleton on a local cluster.  I first copied 'all' profile and created another profile out of it.  Stood up 1st node under ports-default and 2nd under ports-01 set.  Made sure cluster as such is working before starting to setup JMS.

       

      We have a required of setting up JMS in a cluster and to have deliver order.  Hence I followed instructions given on this blogpost.

      http://community.jboss.org/wiki/JBMHASingleton

       

      It I bring just one node under ports-default JMS topic is coming up and working fine.  But, if I try to bring up 2nd node, it does not come up and throws the below given error.

       

      DEPLOYMENTS MISSING DEPENDENCIES:

        Deployment "jboss.jca:name=JmsXA,service=ConnectionFactoryBinding" is missing the following dependencies:

          Dependency "jboss.jca:name=JmsXA,service=TxCM" (should be in state "Create", but is actually in state "Configured")

        Deployment "jboss.jca:name=JmsXA,service=ManagedConnectionFactory" is missing the following dependencies:

          Dependency "jboss.messaging:service=ServerPeer" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.messaging:service=ServerPeer' **")

        Deployment "jboss.jca:name=JmsXA,service=ManagedConnectionPool" is missing the following dependencies:

          Dependency "jboss.jca:name=JmsXA,service=ManagedConnectionFactory" (should be in state "Create", but is actually in state "Configured")

        Deployment "jboss.jca:name=JmsXA,service=TxCM" is missing the following dependencies:

          Dependency "jboss.jca:name=JmsXA,service=ManagedConnectionPool" (should be in state "Create", but is actually in state "Configured")

        Deployment "jboss.messaging:service=PostOffice" is missing the following dependencies:

          Dependency "jboss.messaging:service=ServerPeer" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.messaging:service=ServerPeer' **")

       

       

      DEPLOYMENTS IN ERROR:

        Deployment "jboss.messaging:service=ServerPeer" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.messaging:service=ServerPeer' **

       

      I also tried out http://community.jboss.org/thread/2748 this solution, but did not help much.

       

      Any help is greatly appretiated.  Thanks in advance.

        • 1. Re: Problem setting up JMS on local cluster
          abhijith_p

          I fixed some of the issue and this the last one.  Not able to get why.  Any help would be greatly appreciated.

           

          DEPLOYMENTS MISSING DEPENDENCIES:

            Deployment "jboss.messaging:service=PostOffice" is missing the following dependencies:

              Dependency "jboss.messaging:service=ServerPeer" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.messaging:service=ServerPeer' **")

           

           

          DEPLOYMENTS IN ERROR:

            Deployment "jboss.messaging:service=ServerPeer" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.messaging:service=ServerPeer' **

           

          Thanks

          • 2. Re: Problem setting up JMS on local cluster
            dasmurali

            Hi Abhijith,

             

            Can you try to attach/paste your ServerPeer definition here. This information you can get from <JBOSS_HOME>/server/<YOUR_INSTANCE>/deploy/messaging/messaging-service.xml.

             

            Search for something like below

             

            ServerPeer MBean configuration

             

            Thanks and Regards

            Murali Reddy

            • 3. Re: Problem setting up JMS on local cluster
              abhijith_p

              Hi Krishna,

               

              Thanks for your reply.  Issue was: I had oracle-persistence-service.xml file in deploy folder, but all other files were in deploy-hasingleton folder.  Once I put it in same place as others it worked fine.

               

              thanks,

              Abhijith