MDB not recieving the message not throwing any exception

[hashmukh punamia]

Hi Reza and Ranchers,

This is my MDB code

 


package com.message;

import java.util.Properties;
import javax.ejb.ActivationConfigProperty;
import javax.ejb.MessageDriven;
import javax.jms.Message;
import javax.jms.MessageListener;
import javax.jms.ObjectMessage;
import javax.naming.Context;


@MessageDriven( activationConfig = {
		@ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"),
		@ActivationConfigProperty(propertyName = "destination", propertyValue = "queue/TestMessageExampleA") })
    
public class MessageDrivenConsumerBean implements MessageListener {
    
    public MessageDrivenConsumerBean() {
    }

    public void onMessage(Message message)
    {
        try
        {
            System.out.println("In OnMessage ");
            Properties env = new Properties();
            env.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");
            env.put(Context.PROVIDER_URL, "jnp://localhost:1099");
            env.put(Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces");            
            
            ObjectMessage mess = (ObjectMessage) message;
            TestMessage testMessage = (TestMessage) mess.getObject();
            System.out.println("The Name is: "+testMessage.name);
            
        }
        catch (Exception ex)
        {
            System.out.println("The Error is: "+ex);
        }
    }
    
}

and below is my JMS message sender code

    


package test.message;

import com.message.TestMessage;
import java.util.Properties;
import javax.jms.Connection;
import javax.jms.ConnectionFactory;
import javax.jms.Destination;
import javax.jms.MessageProducer;
import javax.jms.ObjectMessage;
import javax.jms.Session;
import javax.naming.Context;
import javax.naming.InitialContext;


public class MessageProd
{

    
    public static void main(String args[])
    {
       try{
        Properties env = new Properties();
        env.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");
        env.put(Context.PROVIDER_URL, "jnp://localhost:1099");
        env.put(Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces"); 
        InitialContext ic = new InitialContext(env);            
           
           
        ConnectionFactory connfac;
        Connection conn;
        Destination dest;
        Session session;        
        MessageProducer prod;
        

        System.out.println("0");
        connfac = (ConnectionFactory) ic.lookup("QueueConnectionFactory");
        System.out.println("1");
        dest =  (Destination) ic.lookup("queue/TestMessageExampleA");
        System.out.println("2");
        conn = connfac.createConnection();
        System.out.println("3");
        session = conn.createSession(true, Session.AUTO_ACKNOWLEDGE);
        prod = session.createProducer(dest); 
        System.out.println("4");
        ObjectMessage mess = session.createObjectMessage();
        TestMessage testMessage = new TestMessage();
        testMessage.name = "Hash Message has been sent Successfully to MDBAAA";
        System.out.println("5");
        mess.setObject(testMessage);
        System.out.println("6");
        prod.send(mess);
        System.out.println("7");
        session.close();
        conn.close();
        System.out.println("8");
           
     
           
       }
       catch(Exception e)
       {
            System.out.println("Error in Producer "+e);
            e.printStackTrace();
       }
        
    }
}

I have added the following entry in jbossmq-destinations-service.xml

  

  <mbean code="org.jboss.mq.server.jmx.Queue"
	 name="jboss.mq.destination:service=Queue,name=TestMessageExampleA">
    <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
  </mbean>

My JMS sender sends the message but my MDB never reads the message not I am getting any exceptions

You help would be appreciated.

Thanks,
Hash

[Amandeep Singh]

In your MDB code, you are not doing lookup for Destination. :idea:

[hashmukh punamia]

Hi Amandeep,

The destination is already there in the activationConfig.
I dont think we will have to do that explictly when one is using annotations for the same

Thanks,
Hash

[Reza Rahman]

Hash,

Not sure exactly what might be going wrong. Try taking a look at our JBoss example code/build scripts for the book. Perhaps the MDB is not packaged/deployed correctly?

Cheers,
Reza

[Jaikiran Pai]

Which version of JBossAS? Please post the entire console logs. How do you start the JBoss server and how do you deploy the application and the queue?

[hashmukh punamia]

Hi Reza and Pai,

Thanks for your quick reply.

I am using Netbeans6.1RC2 to create a independant EJB module with the MDB code. My EJB module only consists of a MDB.
Then I deploy the ejb module in JBoss4.2.2GA.

  



package testMDB;

import java.util.Properties;
import javax.ejb.ActivationConfigProperty;
import javax.ejb.MessageDriven;
import javax.jms.Message;
import javax.jms.MessageListener;
import javax.jms.ObjectMessage;
import javax.naming.Context;


@MessageDriven(mappedName = "TestMessageExampleA", activationConfig =  {
        @ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "Auto-acknowledge"),
        @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"),
        @ActivationConfigProperty(propertyName = "destination", propertyValue = "queue/TestMessageExampleA")
    })
public class SampleMDBBean implements MessageListener {
    
    public SampleMDBBean() {
    }

    public void onMessage(Message message)
    {
        
        
        try
        {
            System.out.println("In OnMessage ");
            Properties env = new Properties();
            env.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");
            env.put(Context.PROVIDER_URL, "jnp://localhost:1099");
            env.put(Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces");            
            
            ObjectMessage mess = (ObjectMessage) message;
            TestMessage testMessage = (TestMessage) mess.getObject();
            System.out.println("The Name is: "+testMessage.name);
            
        }
        catch (Exception ex)
        {
            System.out.println("The Error is: "+ex);
        }        
        
        
    }
    
}

Now I create a seperate web application project to which I have added a java class (MessageProd.class) running the JMS code similar to the sample code provided in EJB3 in action book.
I am adding the jar file to my library just to get the TestMessage.class.

package test.message;

import java.io.Serializable;
import testMDB.*;
import java.util.Properties;
import javax.jms.Connection;
import javax.jms.ConnectionFactory;
import javax.jms.Destination;
import javax.jms.MessageProducer;
import javax.jms.ObjectMessage;
import javax.jms.Session;
import javax.naming.Context;
import javax.naming.InitialContext;


public class MessageProd
{

    
    public static void main(String args[])
    {
       try{
        Properties env = new Properties();
        env.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");
        env.put(Context.PROVIDER_URL, "jnp://localhost:1099");
        env.put(Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces"); 
        InitialContext ic = new InitialContext(env);            
           
           
        ConnectionFactory connfac;
        Connection conn;
        Destination dest;
        Session session;        
        MessageProducer prod;
        

        System.out.println("0");
        connfac = (ConnectionFactory) ic.lookup("QueueConnectionFactory");
        System.out.println("1");
        dest =  (Destination) ic.lookup("queue/TestMessageExampleA");
        System.out.println("2");
        conn = connfac.createConnection();
        System.out.println("3");
        session = conn.createSession(true, Session.AUTO_ACKNOWLEDGE);
        prod = session.createProducer(dest); 
        System.out.println("4");
        ObjectMessage mess = session.createObjectMessage();
        TestMessage testMessage = new TestMessage();
        testMessage.name = "Hash Message has been sent Successfully to MDB";
        System.out.println("5");
        mess.setObject(testMessage);
        System.out.println("6");
        prod.send(mess);
        System.out.println("7");
        session.close();
        conn.close();
        System.out.println("8");
                 
           
       }
       catch(Exception e)
       {
            System.out.println("Error in Producer "+e);
            e.printStackTrace();
       }
        
    }
}

When I execute the client code I dont get any output on the server.

I have added the following entry in jbossmq-destinations-service.xml

  <mbean code="org.jboss.mq.server.jmx.Queue"
	 name="jboss.mq.destination:service=Queue,name=TestMessageExampleA">
    <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
  </mbean>
 

Also my server startup logs

  


  JBoss Bootstrap Environment

  JBOSS_HOME: C:\jboss-4.2.2.GA

  JAVA: C:\Program Files\Java\jdk1.5.0_12\bin\java

  JAVA_OPTS:  -Dhttp.proxyHost=3.209.124.102 -Dhttp.proxyPort=80 -Dhttp.nonProxyHosts="3.*|*scdev*|*folder*|*.comfin.ge.com|*.capital.ge.com|*.corp.ge.com|*.gesm.ge.com|*.corporate.ge.com|*globaltax.ge.com|lean.ge.com*|*gecis*|*gcpsinggn*|*gcbsinhyd*|*libraries*|inkol*|*scsecuredev*|*icalmscontent*|staging.supportcentral.ge.com*|<local>*|localhost|127.0.0.1|TCS057080" -Dhttps.proxyHost=3.209.124.102 -Dhttps.proxyPort=80 -Dprogram.name=run.bat -server -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000

  CLASSPATH: C:\Program Files\Java\jdk1.5.0_12\lib\tools.jar;C:\jboss-4.2.2.GA\bin\run.jar

===============================================================================

22:22:21,159 INFO  [Server] Starting JBoss (MX MicroKernel)...
22:22:21,159 INFO  [Server] Release ID: JBoss [Trinity] 4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)
22:22:21,159 INFO  [Server] Home Dir: C:\jboss-4.2.2.GA
22:22:21,159 INFO  [Server] Home URL: file:/C:/jboss-4.2.2.GA/
22:22:21,159 INFO  [Server] Patch URL: null
22:22:21,159 INFO  [Server] Server Name: default
22:22:21,159 INFO  [Server] Server Home Dir: C:\jboss-4.2.2.GA\server\default
22:22:21,159 INFO  [Server] Server Home URL: file:/C:/jboss-4.2.2.GA/server/default/
22:22:21,581 INFO  [Server] Server Log Dir: C:\jboss-4.2.2.GA\server\default\log
22:22:21,581 INFO  [Server] Server Temp Dir: C:\jboss-4.2.2.GA\server\default\tmp
22:22:21,581 INFO  [Server] Root Deployment Filename: jboss-service.xml
22:22:22,112 INFO  [ServerInfo] Java version: 1.5.0_12,Sun Microsystems Inc.
22:22:22,112 INFO  [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_12-b04,Sun Microsystems Inc.
22:22:22,112 INFO  [ServerInfo] OS-System: Windows XP 5.1,x86
22:22:23,768 INFO  [Server] Core system initialized
22:22:29,800 INFO  [WebService] Using RMI server codebase: http://127.0.0.1:8083/
22:22:29,800 INFO  [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml
22:22:31,441 INFO  [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
22:22:31,441 INFO  [TransactionManagerService] Setting up property manager MBean and JMX layer
22:22:32,737 INFO  [TransactionManagerService] Starting recovery manager
22:22:33,519 INFO  [TransactionManagerService] Recovery manager started
22:22:33,519 INFO  [TransactionManagerService] Binding TransactionManager JNDI Reference
22:22:45,613 INFO  [EJB3Deployer] Starting java:comp multiplexer
22:22:46,972 INFO  [STDOUT] no object for null
22:22:46,972 INFO  [STDOUT] no object for null
22:22:47,082 INFO  [STDOUT] no object for null
22:22:47,129 INFO  [STDOUT] no object for {urn:jboss:bean-deployer}supplyType
22:22:47,144 INFO  [STDOUT] no object for {urn:jboss:bean-deployer}dependsType
22:22:53,222 INFO  [NativeServerConfig] JBoss Web Services - Native
22:22:53,222 INFO  [NativeServerConfig] jbossws-native-2.0.1.SP2 (build=200710210837)
22:22:57,035 INFO  [Embedded] Catalina naming disabled
22:22:58,801 INFO  [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Java\jdk1.5.0_12\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;C:\Program Files\Microsoft SQL Server\80\Tools\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\;C:\Program Files\Java\jdk1.5.0_06\bin;D:\Sales&UseTax\GEConfidential\Applications\ImageMove;D:\Sales&UseTax\GEConfidential\Applications\ImageMove\acsExtract.jar;D:\Sales&UseTax\GEConfidential\Applications\ImageMove\updateImageTables.jar;D:\TCS Internal\apache-ant-1.7.1-bin\apache-ant-1.7.1\bin;.;
22:23:00,660 INFO  [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0.1-8080
22:23:00,691 INFO  [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009
22:23:00,691 INFO  [Catalina] Initialization processed in 3655 ms
22:23:00,691 INFO  [StandardService] Starting service jboss.web
22:23:00,707 INFO  [StandardEngine] Starting Servlet Engine: JBossWeb/2.0.1.GA

22:23:01,520 INFO  [Catalina] Server startup in 815 ms
22:23:02,567 INFO  [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jboss-web.deployer/ROOT.war/
22:23:03,832 INFO  [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/http-invoker.sar/invoker.war/
22:23:04,332 INFO  [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../deploy/jbossws.sar/jbossws-context.war/
22:23:04,738 INFO  [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
22:23:08,989 INFO  [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../deploy/management/console-mgr.sar/web-console.war/

22:23:09,973 INFO  [MailService] Mail Service bound to java:/Mail
22:23:10,301 INFO  [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-local-jdbc.rar
22:23:10,645 INFO  [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-xa-jdbc.rar
22:23:10,801 INFO  [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-local-jdbc.rar
22:23:10,848 INFO  [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-xa-jdbc.rar
22:23:10,957 INFO  [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jms/jms-ra.rar
22:23:11,020 INFO  [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/mail-ra.rar
22:23:11,520 INFO  [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/quartz-ra.rar
22:23:11,536 INFO  [QuartzResourceAdapter] start quartz!!!
22:23:11,676 INFO  [SimpleThreadPool] Job execution threads will use class loader of thread: main
22:23:11,723 INFO  [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
22:23:11,723 INFO  [RAMJobStore] RAMJobStore initialized.
22:23:11,723 INFO  [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
22:23:11,957 INFO  [StdSchedulerFactory] Quartz scheduler version: 1.5.2
22:23:11,957 INFO  [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
22:23:13,708 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
22:23:14,911 INFO  [A] Bound to JNDI name: queue/A
22:23:14,911 INFO  [B] Bound to JNDI name: queue/B
22:23:14,911 INFO  [C] Bound to JNDI name: queue/C
22:23:14,911 INFO  [D] Bound to JNDI name: queue/D
22:23:14,911 INFO  [ex] Bound to JNDI name: queue/ex
22:23:14,926 INFO  [TestMessageExampleA] Bound to JNDI name: queue/TestMessageExampleA
22:23:14,942 INFO  [testTopic] Bound to JNDI name: topic/testTopic
22:23:14,958 INFO  [securedTopic] Bound to JNDI name: topic/securedTopic
22:23:14,958 INFO  [testDurableTopic] Bound to JNDI name: topic/testDurableTopic
22:23:15,020 INFO  [testQueue] Bound to JNDI name: queue/testQueue
22:23:15,114 INFO  [UILServerILService] JBossMQ UIL service available at : /127.0.0.1:8093
22:23:15,161 INFO  [DLQ] Bound to JNDI name: queue/DLQ
22:23:15,708 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=eaudit' to JNDI name 'java:eaudit'
22:23:15,973 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
22:23:16,286 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=eAuditSales' to JNDI name 'java:eAuditSales'
22:23:16,286 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=test' to JNDI name 'java:test'
22:23:16,911 INFO  [JmxKernelAbstraction] creating wrapper delegate for: org.jboss.ejb3.mdb.MDB
22:23:16,926 INFO  [JmxKernelAbstraction] installing MBean: jboss.j2ee:jar=MDBModule.jar,name=SampleMDBBean,service=EJB3 with dependencies:
22:23:17,239 INFO  [EJBContainer] STARTED EJB: testMDB.SampleMDBBean ejbName: SampleMDBBean
22:23:17,317 INFO  [EJB3Deployer] Deployed: file:/C:/jboss-4.2.2.GA/server/default/deploy/MDBModule.jar

........................
  

Please let me know if I am wrong somewhere

Thanks in advance

Thanks,
Hash

[hashmukh punamia]

Hi Reza,

Its working now.
Able to see the messgae on the console now.

1)
session = conn.createSession(true, Session.AUTO_ACKNOWLEDGE);

The first param should be false

and 2) havent started the connection

Thanks & Regards,
Hash

[Reza Rahman]

Hash,

Glad it worked out.

Best regards,
Reza

P.S.: Please do me a big favor and kindly avoid addressing questions to me directly (especially in the thread starter ) on the JavaRanch forums. The reason is that I am merely just another "Rancher" here, so it looks a little out-of-place and makes me a tiny bit uncomfortable. I try my best to keep an eye on posts anyway and respond when I think it is needed :-). That being said, you can address me directly all you want on the Manning EJB 3 in Action Author Online Forum: http://www.manning.com/panda/. And I understand and appreciate the gesture :-).