In this article we will see how can one send messages to a queue on box-1 and those messages can be received by the consumer from box-2 which is a very basic scenario in most of the people. The main concept for this is that we would be sending messages to the queue on box-1 and on box-2 we would be creating a remote-queue which would have the URL of the JBoss having the queue on box-1 and using that URL remote-queue would connect to the connection factory and would connect to the queue for JBoss which is on box-1. Once we get the access of connection factory and queue we would just create an MDB which would use the same details from remote-queue and would be able to consume message from box-2 easily.

This article has the full configuration for the set-up of remote queue as well as we would also be doing testing to check if our configuration is working fine which the sender code.

Steps to configure an MDB to access a Remote Queue

As we would be access a remote queue we would be need two different physical Machine (i.e. Box-1 and Box-2) for this example as shown below.

In Box-1

Lets say we have a JBoss node in this box called Node-1 and following things has to be done on this box-1

  1. Just put “TestQueue-service.xml” file in the “Node-1/deploy” folder
  2. TestQueue-service.xml

    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
        <mbean xmbean-dd="xmdesc/Queue-xmbean.xml" name="jboss.messaging.destination:service=Queue,name=TestQueue" code="org.jboss.jms.server.destination.QueueService">
            <attribute name="JNDIName">TestQueue</attribute>
            <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>

In Box-2

In this box we have another JBoss node called Node-2 and following things has to be done on this box

  1. Put the “remote-jms-ds.xml” file in the “Node-2/deploy” folder
  2. remote-jms-ds.xml

    <?xml version="1.0" encoding="UTF-8"?>
      <!-- 1. Search XXX in this file and replace it with your remote server name -->
      <!-- Remote JMS Provider configuration -->
      <mbean code="org.jboss.naming.ExternalContext" name="jboss.jndi:service=ExternalContext,jndiName=remote">
        <attribute name="JndiName">remote</attribute>
        <attribute name="Properties">
      <mbean code="org.jboss.jms.jndi.JMSProviderLoader" name="jboss.jms:service=JMSProviderLoader,name=RemoteJMSProvider">
        <attribute name="ProviderName">RemoteJMSProvider</attribute>
        <attribute name="ProviderAdapterClass">org.jboss.jms.jndi.JNDIProviderAdapter</attribute>
        <attribute name="FactoryRef">remote/XAConnectionFactory</attribute>
        <attribute name="QueueFactoryRef">remote/XAConnectionFactory</attribute>
        <attribute name="TopicFactoryRef">remote/XAConnectionFactory</attribute>
        <config-property name="SessionDefaultType" type="java.lang.String">javax.jms.Queue</config-property>
        <config-property name="JmsProviderAdapterJNDI" type="java.lang.String">java:/RemoteJMSProvider</config-property>

    Note: In “remote-jms-ds.xml” file you have to change the XXX with the your remote server name/IP address of the remote server

  3. Put the “MDB3_EAR.ear” files in the “Node-2/deploy” folder
    1. Create a folder called “MDB3_EAR.ear
    2. Under it create 2 folders called “MDB3.jar” and “META-INF
    3. Inside “META-INF” create a “application.xml” file and update this file with the below details
    4. <?xml version="1.0" encoding="UTF-8"?>
      <application version="5" xmlns=""
    5. Inside “MDB3.jar” create a “” file and update this file with the below details
    6. import javax.ejb.MessageDriven;
      import javax.jms.JMSException;
      import javax.jms.Message;
      import javax.jms.MessageListener;
      import javax.jms.TextMessage;
      import javax.ejb.ActivationConfigProperty;
      // To consume messages from REMOTE destination in JBoss AS 6
              @ActivationConfigProperty(propertyName="providerAdapterJNDI", propertyValue="java:/RemoteJMSProvider"),
              @ActivationConfigProperty(propertyName="destinationType", propertyValue="javax.jms.Queue"),
              @ActivationConfigProperty(propertyName="destination", propertyValue="remote/TestQueue"),   //<--  JNDI Name of the Queue on the Remote destionation here its "TestQueue"
              @ActivationConfigProperty(propertyName="useDLQ", propertyValue="false")
      	//************************* RECONNECT PARAMERTERS  *****************************
      	@ActivationConfigProperty(propertyName="reconnectAttempts", propertyValue="60"),
      	@ActivationConfigProperty(propertyName="reconnectInterval", propertyValue="10")
      public class MyMDB implements MessageListener{
          public void onMessage(Message message) {
              TextMessage textMessage = (TextMessage) message;
              try {
                  System.out.println("nnt Message has been Received by MDB : "+ textMessage.getText());
              } catch (JMSException e) {
    7. Once every think has been put at its place, then you can compile the java code and if wanted create an EAR archive file for above folder
  4. You would have to put the following “application-policy” block to the “conf/login-config.xml
  5. <application-policy name="RemoteJmsXARealm">
        <login-module code="" flag="required">
          <module-option name="principal">guest</module-option>
          <module-option name="userName">guest</module-option>
          <module-option name="password">guest</module-option>
          <module-option name="managedConnectionFactoryName">jboss.jca:service=TxCM,name=RemoteJmsXA</module-option>

After following the above given steps, we have successfully configured all the setting from JBoss end. Now its time to test our configuration by following the below steps.


  1. Create a Directory somewhere in your file system like: “/urs/JBoss/JBM/Queue” to write the and as we have an MDB we would not need a programs.
  2. In copy the below program
    import java.util.Hashtable;
    import javax.jms.JMSException;
    import javax.jms.Queue;
    import javax.jms.QueueConnection;
    import javax.jms.QueueConnectionFactory;
    import javax.jms.QueueSender;
    import javax.jms.QueueSession;
    import javax.jms.Session;
    import javax.jms.TextMessage;
    import javax.naming.Context;
    import javax.naming.InitialContext;
    import javax.naming.NamingException;
    public class QueueSend
    public final static String JNDI_FACTORY="org.jnp.interfaces.NamingContextFactory";
    //*************** Connection Factory JNDI name *************************
    public final static String JMS_FACTORY="/ConnectionFactory";
    //*************** Queue JNDI name *************************
    public final static String QUEUE="/TestQueue";
    private QueueConnectionFactory qconFactory;
    private QueueConnection qcon;
    private QueueSession qsession;
    private QueueSender qsender;
    private Queue queue;
    private TextMessage msg;
    public void init(Context ctx, String queueName)throws NamingException, JMSException
    qconFactory = (QueueConnectionFactory) ctx.lookup(JMS_FACTORY);
    qcon = qconFactory.createQueueConnection();
    qsession = qcon.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
    queue = (Queue) ctx.lookup(queueName);
    qsender = qsession.createSender(queue);
    msg = qsession.createTextMessage();
    public void send(String message) throws JMSException {
    public void close() throws JMSException {
    public static void main(String[] args) throws Exception {
    if (args.length != 1) {
    System.out.println("Usage: java QueueSend URL");
    InitialContext ic = getInitialContext(args[0]);
    QueueSend qs = new QueueSend();
    qs.init(ic, QUEUE);
    private static void readAndSend(QueueSend qs) throws IOException, JMSException
    String line="Test Message Body with counter = ";
    BufferedReader br=new BufferedReader(new InputStreamReader(;
    boolean readFlag=true;
    System.out.println("ntStart Sending Messages (Enter QUIT to Stop):n");
    System.out.print("<Msg_Sender> ");
    String msg=br.readLine();
    if(msg.equals("QUIT") || msg.equals("quit"))
    private static InitialContext getInitialContext(String url) throws NamingException
    Hashtable env = new Hashtable();
    env.put(Context.PROVIDER_URL, url);
    return new InitialContext(env);
  3. Now open just 1– command prompt and run the “. ./” by adding two DOTs separated by a single space, in both the prompts to set the Environment (PATH & CLASSPATH).

    echo "Exporting JBOSS_HOME...."
    export JBOSS_HOME=/Jboss/AS6/jboss-as   #<---- Change as per your environment
    echo "JBOSS_HOME Exported....!!!"
    echo ""
    echo "Exporting JAVA_HOME...."
    export JAVA_HOME=/Jdk/jdk1.6.0_21    #<---- Change as per your environment
    echo "JBOSS_HOME Exported....!!!"
    echo ""
    echo "Exporting CLASSPATH...."
    export CLASSPATH=$JBOSS_HOME/client/jbossall-client.jar:$JBOSS_HOME/client/jboss-javaee.jar:$JBOSS_HOME/common/lib/jnpserver.jar:$JBOSS_HOME/client/jboss-logging-spi.jar:$JBOSS_HOME/lib/jboss-javaee.jar:$JBOSS_HOME/common/lib/servlet-api.jar:$JBOSS_HOME/common/lib/log4j.jar:$CLASSPATH:.:
    echo "CLASSPATH Exported....!!!"
    echo ""
    echo "Exporting PATH...."
    export PATH=$JAVA_HOME/bin:$PATH
    echo "PATH Exported....!!!"
    echo ""
    echo "========================================================================"
    echo "JBOSS_HOME = " $JBOSS_HOME
    echo ""
    echo "JAVA_HOME = " $JAVA_HOME
    echo ""
    echo ""
    echo "PATH = " $PATH
    echo "========================================================================"
  5. Then compile the programs.
  6. Now run the code with the following command
  7. Prompt-1

    java QueueSend jnp://IP_BOX-1:1099
  8. Once this is been done try to send some messages in the Prompt-1 which can be revived on Prompt-2.

Once everything is up and running properly you just have to send around few messages in “Prompt-1” and you would notice that those messages would be shown in shell on which the Node-2 is running which is on Box-2. Hence when you are sending a messages to the queue which is on Box-1 the same messages are been consumed by the MDB allocation deployed on Node-2 running on Box-2

If you enjoyed this post, please consider leaving a comment or subscribing to the RSS feed to have future articles delivered to your feed reader.