1 Reply Latest reply on Jul 30, 2007 1:23 PM by tnine

    EAR does not correctly deploy EJB3 MDB

    tnine Newbie

      Hi all,
      I have an ear with an MDB that connects to a spring POJO. The deployment is very simple and the ear deploys correctly, however the MDB never reads from the queue, nor can I see my scoped classloader, or the EJB in the JMX console. I'm using JBoss 4.0.2, and an EJB3 MDB. I have included my configuration. The ear does contain all of the neccessary files (I think), and I'm not sure what's going on. Here are my configuration files.

      In the ear




      MDB class
       * @author Todd Nine
      @MessageDriven(activationConfig =
      @ActivationConfigProperty(propertyName="destinationType", propertyValue="javax.jms.Queue"),
      @ActivationConfigProperty(propertyName="destination", propertyValue="queue/StatementInput")
      public class StatementMessageDrivenBean extends AbstractJmsMessageDrivenBean {
       * (non-Javadoc)
       * @see javax.jms.MessageListener#onMessage(javax.jms.Message)
       public void onMessage(Message message) {...}

      I know the queue is set up correctly, I'm able to push messaged onto it, and they are correctly persisted. This is a high availability JBoss MQ installation, do I need to set any special properties in my annotations to read from it?

        • 1. Re: EAR does not correctly deploy EJB3 MDB
          tnine Newbie

          Just for a follow up, it does work with my 2.0 descriptions. Am I missing something with my 3.0 annotations?


          <?xml version="1.0" encoding="UTF-8"?>
          <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN"
           <description>Message Driven Bean</description>
           <display-name>Statements Message Driven Bean</display-name>
           <!--Define our EJBs-->
           <!-- Define our MDB for statements-->
           Bean to access messages statement input queue
           <display-name>Statement Bean</display-name>
           <!-- make our EJB an XA transaction -->

          <?xml version='1.0' encoding='UTF-8' ?>
          <!DOCTYPE jboss PUBLIC
           "-//JBoss//DTD JBOSS 4.0//EN"