3 Replies Latest reply on Apr 8, 2004 3:19 PM by ftftft

    JBOSS subscribe Weblogic JMS Topic

    ftftft Newbie

      I want to listen to subscribe weblogic topic from jboss. I see many people ask almost the same question, however, no solution yet. I'm curious to know it is doable or not. If not, I stop trying. The follow is my trial.

      1) I follow the FAQ and write a simple WeblogicMQProvider. The deployments seems right. But it just doesn't work.

      ----Question:
      ----How do I configure an MDB to talk to remote queue.
      ----Answer:
      ----You need to configure a remote provider (this is similar to local one in jms-ds.xml)
      ----3) Use external Queue/Topic ConnectionFactory

      I don't see the follow configuration use external Topic ConnectionFactory.

      2) I try ExternalContext. When I want to use JNDIView to see the JNDI tree, it never return untill "out of memory".

      Thanks in advance.

        • 1. Re: JBOSS subscribe Weblogic JMS Topic
          Adrian Brock Master

          I've seen lots of posts like this.
          People say they can't get it work but never post what the error message is
          or what is not working.

          The jndi view problem is probably due to some sort of recursion
          in your jndi tree. Due to one part of the tree including another part and vice versa.
          Adding the following property to the external context mbean might help fix it:

          <attribute name="RemoteAccess">false</attribute>
          


          Regards,
          Adrian


          • 2. Re: JBOSS subscribe Weblogic JMS Topic
            ftftft Newbie

            Thanks adrian. I believe there is no error message in the console. That is the reason no one post the error message.

            I find the follow link that provide a sample to link websphere and jboss.

            http://sourceforge.net/tracker/index.php?func=detail&aid=753022&group_id=22866&atid=376687

            but I cannot download the sample code. Where can I find the file?

            "adrian@jboss.org" wrote:
            I've seen lots of posts like this.
            People say they can't get it work but never post what the error message is
            or what is not working.

            The jndi view problem is probably due to some sort of recursion
            in your jndi tree. Due to one part of the tree including another part and vice versa.
            Adding the following property to the external context mbean might help fix it:
            <attribute name="RemoteAccess">false</attribute>
            


            Regards,
            Adrian


            • 3. Re: JBOSS subscribe Weblogic JMS Topic
              ftftft Newbie

              Finally, I move forward a little bit and get the follow exception. Would you help me figure it out? Thanks a lot.

              2004-04-08 16:00:51,204 DEBUG [WeblogicMQProvider] connecting to remote JNDI with props: {java.naming.provider.url=t3://192.168.1.152:80, java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory}
              2004-04-08 16:00:51,205 DEBUG [WeblogicMQProvider] props information javax.naming.InitialContext@a6997
              2004-04-08 16:00:51,205 DEBUG [WeblogicMQProvider] created context: javax.naming.InitialContext@a6997
              2004-04-08 16:00:51,209 ERROR [org.jboss.ejb.plugins.jms.DLQHandler] Initialization failed
              javax.jms.JMSException: Error creating the dlq connection: Unhandled exception in lookup
              at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:169)
              at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:158)
              at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerCreate(JMSContainerInvoker.java:458)


              "adrian@jboss.org" wrote:
              I've seen lots of posts like this.
              People say they can't get it work but never post what the error message is
              or what is not working.

              The jndi view problem is probably due to some sort of recursion
              in your jndi tree. Due to one part of the tree including another part and vice versa.
              Adding the following property to the external context mbean might help fix it:
              <attribute name="RemoteAccess">false</attribute>
              


              Regards,
              Adrian