2 Replies Latest reply on Aug 12, 2004 3:38 AM by ammon sekhemt

    Clustered MDB - jboss 3.2.5

    ammon sekhemt Newbie

      I have 2 jboss 3.2.5 instance in cluster. I have deploy a MDB on both the instance . When I write on the topic the messages come consume from both the MDB. Is It possible to put in cluster also the two MDB??
      moreover when a request also falls the messages if rendered persistent does not come read from the new MDB in the new node master.

      Do you have a suggestion?
      thanks

        • 1. Re: Clustered MDB - jboss 3.2.5
          leomad6 Newbie

          hey Nadaya

          did you deploy MDB across cluster, i.e. farm dir. Or did you deploy the MDB individually in each node of the cluster.
          coz I need to configure an MDB(in cluster) to listen to a topic where a message to topic is subscribed by all the instances of MDB across cluster.
          If yes, can you tell me what files you changed to attain this.

          Thanks in advance.

          • 2. Re: Clustered MDB - jboss 3.2.5
            ammon sekhemt Newbie

            Hello leomad6. I have deploied in every node of the cluster. The files are following:
            jboss.xml

            <?xml version="1.0"?>
            <jboss>
             <invoker-proxy-binding>
             <name>message-driven-bean</name>
             <invoker-mbean>default</invoker-mbean>
             <proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory>
             <proxy-factory-config>
            <JMSProviderAdapterJNDI>DefaultJMSProvider</JMSProviderAdapterJNDI>
            <ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI>
             <MinimumSize>1</MinimumSize>
             <MaximumSize>15</MaximumSize>
             <KeepAliveMillis>30000</KeepAliveMillis>
             <MaxMessages>1</MaxMessages>
             <MDBConfig>
             <ReconnectIntervalSec>10</ReconnectIntervalSec>
             <DLQConfig>
             <DestinationQueue>queue/DLQ</DestinationQueue>
             <MaxTimesRedelivered>10</MaxTimesRedelivered>
             <TimeToLive>0</TimeToLive>
             <DLQUser>john</DLQUser>
             <DLQPassword>needle</DLQPassword>
             </DLQConfig>
             </MDBConfig>
             </proxy-factory-config>
             </invoker-proxy-binding>
             <invoker-proxy-binding>
             <name>singleton-message-driven-bean</name>
             <invoker-mbean>default</invoker-mbean>
             <proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory>
             <proxy-factory-config>
             <JMSProviderAdapterJNDI>DefaultJMSProvider</JMSProviderAdapterJNDI>
             <ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI>
             <!-- WARN: Don't set this to zero until a bug in the pooled executor is fixed -->
             <MinimumSize>1</MinimumSize>
             <MaximumSize>1</MaximumSize>
             <KeepAliveMillis>30000</KeepAliveMillis>
             <MaxMessages>1</MaxMessages>
             <MDBConfig>
             <ReconnectIntervalSec>10</ReconnectIntervalSec>
             <DLQConfig>
             <DestinationQueue>queue/DLQ</DestinationQueue>
             <MaxTimesRedelivered>10</MaxTimesRedelivered>
             <TimeToLive>0</TimeToLive>
             <DLQUser>john</DLQUser>
             <DLQPassword>needle</DLQPassword>
             </DLQConfig>
             </MDBConfig>
             </proxy-factory-config>
             </invoker-proxy-binding>
             <enterprise-beans>
             <message-driven>
             <ejb-name>TextMDB</ejb-name>
             <destination-jndi-name>topic/testTopic</destination-jndi-name>
             <resource-ref>
             <res-ref-name>jms/testTopic</res-ref-name>
             <jndi-name>ConnectionFactory</jndi-name>
             </resource-ref>
             <mdb-user>john</mdb-user>
             <mdb-passwd>needle</mdb-passwd>
             </message-driven>
             </enterprise-beans>
            </jboss>


            As client I have used the DUrableTopicClient.java example of the documentation.
            In this situation when the node master goes in failover according to node beyond losing the messages from an error on the XAConnectionFactory. You have an idea?
            Bye