1 Reply Latest reply on Jan 26, 2004 2:18 AM by Volker Sommerfeld

    How to subscribe a message driven bean to a topic on remote

    Volker Sommerfeld Newbie

       

      "VolleSommi67" wrote:
      Hi,

      I'm new with the JBOSS server and I have a problem while trying to subscribe a MDB to topics that are on remote JBOSS 3.2.1 servers:

      That is, on server A is a MDB. On servers B and C are session beans that publishes messages to a topic on server B or C, respectively. How can the MDB on server A succesfully subscribe to the topics on servers B and C? What configuration files must be changed at servers A, B and C, and in which way?

      I'd appreciate some useful hints because all information that I've found to this problem doesn't really help me.

      Best wishes,
      Volker


        • 1. Re: How to subscribe a message driven bean to a topic on rem
          Volker Sommerfeld Newbie

          I tried the following (see FAQ answered by Adrian) in order to subscribe a message driven bean to a topic on remote server, but I didn't succeed. What did I wrong?

          1) Definition of a JMS remote provider in a *-service.xml:
          <!-- The JMS Remote provider loader -->

          NT95JMSProvider
          jnp://nt95:1099

          org.jboss.jms.jndi.JBossMQProvider

          java:/XAConnectionFactory
          java:/XAConnectionFactory



          2) Definition of a invoker-proxy.binding for the JMS remote provider in the standardjboss.xml:
          <invoker-proxy-binding>
          RepositoryServerUpdateProcessorBinding
          <invoker-mbean>whatever</invoker-mbean>
          <proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory>
          <proxy-factory-config>
          NT95JMSProvider
          StdJMSPool
          15
          10

          10

          queue/DLQ
          10
          0


          </proxy-factory-config>
          </invoker-proxy-binding>

          3) Reference to the invoker-proxy-binding in the jboss.xml:
          <message-driven>
          <ejb-name>RepositoryServerUpdateProcessor</ejb-name>
          <destination-jndi-name>topic/repositoryUpdateTopic</destination-jndi-name>
          <invoker-bindings>
          <invoker-proxy-binding-name>RepositoryServerUpdateProcessorBinding</invoker-proxy-binding-name>
          </invoker-bindings>
          </message-driven>


          By the way, it is also possible to use a clustered JMS notification service that is available since JBOSS 3.2.3 (see http://www.onjava.com/pub/a/onjava/2003/08/20/jboss_clustering.html?page=2)?

          I'd really appreciate some hints!!!

          Best wishes,
          Volker