1 2 Previous Next 19 Replies Latest reply on Feb 5, 2010 8:08 AM by rasa Go to original post
      • 15. Re: Multiple Jboss configuration using jboss 4.2.3 GA
        rasa
        Queue look up is working perfectly, it is not giving any error. Using my JMSprovider's option i can view the queue that has bounded. So why this message sending is fails. Is it because of any version related issues. Please guide me to solve this headache.
        • 16. Re: Multiple Jboss configuration using jboss 4.2.3 GA
          peterj

          "Please guide me to solve this headache."

           

          Please be more precise in your posts - the vagueness of your posts has made it very difficult to even determine what the problem is, much less to come up with a solution. Here is an example:

           

          In my prior post I asked you to first try sending messages to the second instance using a standalone client. Did you try this and did it work? Is this what you mean by "Queue look up is working perfectly"?

           

          I also wrote that if sending messages to the second instance from a standalone client works, that we can then look at the code in the first instance that is trying to send messages. So when you say "Queue look up is working perfectly", are you talking about the code in the first instance?

           

          You then follow that statement with "Using my JMSprovider's option i can view the queue that has bounded." which sounds like you are using some tool to view the queue. So is that waht you mean by "Queue look up is working perfectly"?

           

          So you see, I have no idea whatsoever about what is and is not working on your system because your statement could mean anything.

           

           

          "Using my JMSprovider's option"

           

          What is "JMSprovider", and what is this "option" of which you speak? To me, "JMSprovider" mean "JBossMQ", but you speak as if it is a tool with "options" and not a piece of middleware with an API. (You are using JBossMQ, which comes with AS 4.2.3, right???)

           

          "Is it because of any version related issues."

           

          I assume that both app server instances are 4.2.3. In that case there are no version issues.

          • 17. Re: Multiple Jboss configuration using jboss 4.2.3 GA
            rasa

            Hi,

             

            As you pointed out, with one instance also it is not working.

             

            19:38:06,485 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

            --- MBeans waiting for other MBeans ---
            ObjectName: jboss.j2ee:jndiName=local/myqueue@22440366,service=EJB
              State: NOTYETINSTALLED
              I Depend On:
                jboss.j2ee:jndiName=local/QueueRecMDB,service=EJB,plugin=invoker,binding=Receiving-message-driven-bean

            May be because of the error.  The last line which i have given here is standardjboss.xml entry. Is there any difference in configuration of standardjboss of 3.2.5 and 4.2.3 GA.

            • 18. Re: Multiple Jboss configuration using jboss 4.2.3 GA
              peterj

              What you just now posted is the deployment summary report printed near the end of startup. That report rarely has any information helpful in solving problems. There should be an error exception stack trace earlier in the console log that indicates the cause for the deployment failure.

               

              "Is there any difference in configuration of standardjboss of 3.2.5 and 4.2.3 GA."

               

              Doing a diff between the files should point out any differences.

              • 19. Re: Multiple Jboss configuration using jboss 4.2.3 GA
                rasa

                Sorry by mistake i clciked Answered correct.

                 

                It is working fine for single instance. But in the case of 2 instance it is not working. Let me explain the scenario.

                 

                In my application i am using second instance as ejb container for only sendign the messages to different destinations. So my java classes which generates the messages are there in the first instance. MDB are deployed in second instance. So there is no need of standardjboss configuration needed in first instance ( i hope so). The configuration which i did for single instance message sending is copied to second instance since that is configured as the messaging container (ejb container for MDB ). Now in first instance i am getting following warning ( remeber my first instance is not the mdb container )

                [JMSContainerInvoker] creating a new temporary destination: queue/test_msg_center

                17:11:45,249 INFO  [test_msg_center] Bound to JNDI name: queue/test_msg_center.

                I think all the message destinations names are given in my ejb-jar.xml of my apps in container-transaction tag. But this is not affecting in my old 3.2.5 setup. Is there any issue with the design. I can't give full design here since my client won't allow that. But i can send a private message.

                 

                 

                Thanks and Regards

                Rasa

                1 2 Previous Next