8 Replies Latest reply on Sep 25, 2003 1:29 AM by Stephane Nicoll

    Failed to look up from one JBOSS to another using an MDB

    karumady Newbie




      hai friends


      In my application a MDB from one JBOSS is trying to listen the topic of another JBOSS running

      on a remote machine. For that I ve created a JMS provider loader for the remote machine in

      my jms-service.xml and given the name in the standardjboss.xml like

      RemoteJMSProvider

      It is looking up the provider adapter .


      The log shows..

      ================================
      [JMSContainerInvoker] Starting
      [JMSContainerInvoker] Initializing
      [JMSContainerInvoker] Looking up provider adapter: java:/RemoteJMSProvider
      [JMSContainerInvoker] Provider adapter: org.jboss.jms.jndi.JBossMQProvider@d6b059
      [DLQHandler] Creating
      [DLQHandler] Using factory: org.jboss.mq.SpyXAConnectionFactory@d47f59
      [DLQHandler] Created connection: org.jboss.mq.SpyConnection@aa17c3
      [DLQHandler] Using Queue: QUEUE.DLQ
      [DLQHandler] Created
      ================================

      But it can't find the destination
      The error is ...

      ================================
      01:47:09,000 WARN [JMSContainerInvoker] JMS provider failure detected:
      javax.jms.JMSException: The destination TOPIC.risTopic does not exist !
      at org.jboss.mq.server.ClientConsumer.addSubscription(ClientConsumer.java:141)
      at org.jboss.mq.server.JMSDestinationManager.subscribe(JMSDestinationManager.java:604)
      at org.jboss.mq.server.JMSServerInterceptorSupport.subscribe(JMSServerInterceptorSupport.java:296)
      at org.jboss.mq.security.ServerSecurityInterceptor.subscribe(ServerSecurityInterceptor.java:143)
      at org.jboss.mq.server.TracingInterceptor.subscribe(TracingInterceptor.java:599)
      at org.jboss.mq.server.JMSServerInvoker.subscribe(JMSServerInvoker.java:298)
      at org.jboss.mq.il.jvm.JVMServerIL.subscribe(JVMServerIL.java:315)
      at org.jboss.mq.Connection.addConsumer(Connection.java:962)
      at org.jboss.mq.SpyConnectionConsumer.(SpyConnectionConsumer.java:73)
      at org.jboss.mq.SpyConnection.createConnectionConsumer(SpyConnection.java:92)
      at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerCreate(JMSContainerInvoker.java:733)
      at org.jboss.ejb.plugins.jms.JMSContainerInvoker.startService(JMSContainerInvoker.java:824)
      at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:164)
      at org.jboss.ejb.MessageDrivenContainer.start(MessageDrivenContainer.java:200)
      at org.jboss.ejb.Container.invoke(Container.java:756)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
      at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:976)
      =================================

      NB: I could able to listen the topic by using a simple java program without using

      JBOSS and MDB.

      Hoping for help...

        • 1. Re: Failed to look up from one JBOSS to another using an MDB
          Adrian Brock Master

          What is the config for RemoteJMSProvider.

          Have you specified a ProviderURL?

          Regards,
          Adrian

          • 2. Re: Failed to look up from one JBOSS to another using an MDB
            karumady Newbie


            Thanks Adrian

            Here is the RemoteJMSProvider



            RemoteJMSProvider
            org.jboss.jms.jndi.JBossMQProvider
            192.168.110.51:1099
            java:/XAConnectionFactory
            java:/XAConnectionFactory

            • 3. Re: Failed to look up from one JBOSS to another using an MDB
              Adrian Brock Master

              You cannot use java:/XAConnectionFactory for remote
              message. You should use XAConnectionFactory or
              UIL2ConnectionFactory.

              Regards,
              Adrian

              • 4. Re: Failed to look up from one JBOSS to another using an MDB
                karumady Newbie


                Thaks Adrian it worked well with 3.0.3

                Sorry for a late reply.......

                But when I just changed the IP in the RemoteJMSProvider and tried to listen topic on 3.0.6
                it gives the errors

                jboss.j2ee:jndiName=local/RisOrderSubscriberBean,service=EJB state: null
                , short name: hl7-1.0.jar, parent short name: null
                12:20:50,521 INFO [EjbModule] Starting
                12:20:50,521 DEBUG [EjbModule] Application.start(), start container: org.jboss.ejb.MessageDrivenContainer@1ef7de4
                12:20:50,521 DEBUG [MessageDrivenContainer] Begin java:comp/env for EJB: RisOrderSubscriberBean
                12:20:50,521 DEBUG [MessageDrivenContainer] TCL: java.net.URLClassLoader@19518cc
                12:20:50,521 DEBUG [MessageDrivenContainer] End java:comp/env for EJB: RisOrderSubscriberBean
                12:20:50,521 DEBUG [BaseLocalContainerInvoker] RisOrderSubscriberBean cannot be Bound, doesn't have local and local home interfaces
                12:20:50,521 INFO [JMSContainerInvoker] Starting
                12:20:50,521 DEBUG [JMSContainerInvoker] Initializing
                12:20:50,536 DEBUG [JMSContainerInvoker] Looking up provider adapter: java:/RemoteJMSProvider
                12:20:50,536 DEBUG [JMSContainerInvoker] Provider adapter: org.jboss.jms.jndi.JBossMQProvider@196f4b5
                12:20:50,536 INFO [DLQHandler] Creating
                12:20:53,849 ERROR [DLQHandler] Initialization failed
                javax.naming.CommunicationException. Root exception is
                java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is:
                java.net.ConnectException: Connection refused: connect
                at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:567)
                at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
                at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
                at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:101)
                at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)
                at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:456)
                at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:440)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:121)
                at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:136)
                at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerCreate(JMSContainerInvoker.java:608)
                at org.jboss.ejb.plugins.jms.JMSContainerInvoker.startService(JMSContainerInvoker.java:824)
                at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:164)
                at org.jboss.ejb.MessageDrivenContainer.start(MessageDrivenContainer.java:200)
                at org.jboss.ejb.Container.invoke(Container.java:756)
                at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
                at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:976)
                at $Proxy5.start(Unknown Source)
                at org.jboss.system.ServiceController.start(ServiceController.java:397)
                at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
                at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                at java.lang.reflect.Method.invoke(Method.java:324)
                at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
                at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
                at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
                at $Proxy40.start(Unknown Source)
                at org.jboss.ejb.EjbModule.startService(EjbModule.java:430)
                at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:164)
                at sun.reflect.GeneratedMethodAccessor23.invoke(Unknown Source)
                at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                at java.lang.reflect.Method.invoke(Method.java:324)
                at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
                at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
                at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:976)
                at $Proxy5.start(Unknown Source)
                at org.jboss.system.ServiceController.start(ServiceController.java:397)


                expecting a quick comment

                • 5. Re: Failed to look up from one JBOSS to another using an MDB
                  Adrian Brock Master

                  Check /etc/hosts

                  Regards,
                  Adrian

                  • 6. Re: Failed to look up from one JBOSS to another using an MDB
                    karumady Newbie



                    Great .It worked.
                    Thanks...................

                    Plz explain me what is happening???
                    is it looking up through the /etc/hosts ???

                    hoping for u'r reply

                    • 7. Re: Failed to look up from one JBOSS to another using an MDB
                      karumady Newbie


                      Continuing the discussion......

                      Now I want to lookup the topics in two different JBOSSs
                      do I need to create another provider adapter ??.
                      If so where should I write my second JMSProviderAdapterJNDI??
                      (in jboss.xml ??, First is in the standardjboss.xml)

                      expecting comments

                      .....thanks

                      • 8. Re: Failed to look up from one JBOSS to another using an MDB
                        Stephane Nicoll Master

                        # Start a new thread for new question
                        # Adrian already replied to that question a couple of days ago, use search

                        Regards,

                        Stephane