3 Replies Latest reply on Apr 29, 2004 6:30 PM by jason1

    Solution for load-balancing MDBs in 3.2.4RC2 HA-JMS

    jason1 Newbie

      I'm using 3.2.4RC2 (April 13th drop), which according to Adrian doesn't have load-balancing capabilities for MDBs across a cluster. So, I thought I'd post my solution for load-balanced, fault-tolerant MDBs that use the new HA-JMS in a cluster.

      My application looks like this:

      1. MDBs deployed in /farm directory across several JBoss servers in a cluster. MDBs in remote JBoss servers connect to the singleton, remote HA-JMS resources while the locally deployed MDBs connect locally.
      2. Oracle DB configured as a shared resource for JMS tables
      3. custom JMS Provider used to connect to the singleton HA-JMS from the other clustered JBoss servers via HA-JNDI.

      When the singleton HA-JMS server fails and another is selected, the custom JMS Provider re-connects (DLQHandlers, JMSContainerInvoker, etc.) to the new master node's resources. The locally deployed MDBs process more messages than the others because of their proximity to the JMS destinations.

      I've tested it and it seems to process messages fine (none lost, load-balancing really works, fail-over of JMSContainerInvoker and its DLQHandlers is seamless except for a few annoying but harmless error messages that get logged when trying to stop an already disconnected JMS SpyConnection, etc.).

      Steps to get it setup (see listings below):
      1. I turned logging in log4j.xml for the org.jnp.NamingContext to ERROR, so it doesn't log each attempt in HA-JNDI that fails as a WARN. Keeps logs cleaner.
      2. You have to build and deploy the custom JMS Provider listed below into a Jar and put it into the /deploy/jms directory.
      3. jms-ds.xml must be changed to reference the new Jar (cdot-jbossx.jar in my case)
      4. jms-ds.xml must point to the new, custom JMS Provider class.

      This solution is only for clustered (e.g., /all). It is not meant to work in standalone-mode, so don't try to use the custom JMS Provider in the default server.

      Custom JMS Provider code (modified from original JBossMQProvider):

       * Copyright (c) 2000 Peter Antman DN <peter.antman@dn.se>
       * This library is free software; you can redistribute it and/or
       * modify it under the terms of the GNU Lesser General Public
       * License as published by the Free Software Foundation; either
       * version 2 of the License, or (at your option) any later version
       * This library is distributed in the hope that it will be useful,
       * but WITHOUT ANY WARRANTY; without even the implied warranty of
       * Lesser General Public License for more details.
       * You should have received a copy of the GNU Lesser General Public
       * License along with this library; if not, write to the Free Software
       * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
      package cdot.jboss;
      import java.util.Hashtable;
      import javax.naming.Context;
      import javax.naming.InitialContext;
      import javax.naming.NamingException;
      import org.apache.commons.logging.Log;
      import org.apache.commons.logging.LogFactory;
      import org.jboss.jms.jndi.AbstractJMSProviderAdapter;
       * A JMS provider adapter for <em>JBossMQ</em> that can fail-over to
       * another JMS server automatically using the HA-JNDI lookup mechanism.
       * Created: Fri Dec 22 09:34:04 2000
       * 6/22/01 - hchirino - The queue/topic jndi references are now configed via JMX
       * 4/27/04 - jwestra - Uses HA-JNDI settings to make InitialContext
       * @version <pre>$Revision: 1.9 $</pre>
       * @author <a href="mailto:peter.antman@dn.se">Peter Antman</a>
       * @author <a href="mailto:cojonudo14@hotmail.com">Hiram Chirino</a>
       * @author <a href="mailto:jason@planet57.com">Jason Dillon</a>
       * @author <a href="mailto:jwestra@csc.com">Jason Westra</a>
      public class JBossMQProvider
       extends AbstractJMSProviderAdapter
       /** The initial context factory to use. */
       public static final String INITIAL_CONTEXT_FACTORY =
       /** The url package prefixes. */
       public static final String URL_PKG_PREFIXES =
       /** The security manager to use. */
       private static final String SECURITY_MANAGER =
       /** Instance logger. */
       private transient Log log = LogFactory.getLog("cdot.jboss.JBossMQProvider");
       /** Flag to enable JNDI security manager. */
       private String hasJndiSecurityManager = "yes";
       * Default no-argument constructor.
       public JBossMQProvider() {
       // empty
       /** Override of standard de-serialization to re-create logger. */
       private void readObject(java.io.ObjectInputStream in)
       throws java.io.IOException, ClassNotFoundException
       this.log = LogFactory.getLog("cdot.jboss.JBossMQProvider");
       * Create a new InitialContext suitable for this JMS provider.
       * @return An InitialContext suitable for this JMS provider.
       * @throws NamingException Failed to construct context.
       public Context getInitialContext() throws NamingException {
       Context ctx = null;
       boolean debug = log.isDebugEnabled();
       try {
       // uses HA-JNDI settings to provide lookup of InitialContext
       Hashtable props = new Hashtable();
       props.put(Context.PROVIDER_URL, providerURL);
       props.put(SECURITY_MANAGER, hasJndiSecurityManager);
       props.put(Context.URL_PKG_PREFIXES, URL_PKG_PREFIXES);
       if (debug)
       log.debug("connecting to remote JNDI with props: " + props);
       ctx = new InitialContext(props);
       // sanity check... can remove later
       String connectionFactoryRef = this.getQueueFactoryRef();
       // end sanity check
       if (debug) {
       log.debug("created context: " + ctx.getEnvironment());
       } catch(Throwable t) {
       NamingException ex = new NamingException(t.getMessage());
       throw ex;
       return ctx;


       <!-- ==================================================================== -->
       <!-- JMS Stuff -->
       <!-- 1.) added classpath setting for custom JMSProvider -->
       <!-- 2.) added provider URLs for clustered JMS -->
       <!-- ==================================================================== -->
       <classpath codebase="deploy/jms" archives="cdot-jbossx.jar"/>
       <!-- The JMS provider loader -->
       <mbean code="org.jboss.jms.jndi.JMSProviderLoader"
       <attribute name="ProviderName">DefaultJMSProvider</attribute>
       <attribute name="ProviderAdapterClass">cdot.jboss.JBossMQProvider</attribute>
       <attribute name="ProviderUrl">localhost:1100,,</attribute>
       <attribute name="QueueFactoryRef">XAConnectionFactory</attribute>
       <attribute name="TopicFactoryRef">XAConnectionFactory</attribute>
       <!-- The server session pool for Message Driven Beans -->
       <mbean code="org.jboss.jms.asf.ServerSessionPoolLoader"
       <depends optional-attribute-name="XidFactory">jboss:service=XidFactory</depends>
       <attribute name="PoolName">StdJMSPool</attribute>
       <attribute name="PoolFactoryClass">
       <!-- JMS XA Resource adapter, use this to get transacted JMS in beans -->
       <adapter-display-name>JMS Adapter</adapter-display-name>
       <config-property name="SessionDefaultType" type="java.lang.String">javax.jms.Topic</config-property>


      <!-- Limit JNP categories to ERROR. This avoids pesky WARNs about fails to connect to HA-JNDI -->
       <category name="org.jnp.interfaces.NamingContext">
       <priority value="ERROR"/>