MessageDrivenBean not really deployed

Question

          I am using 6.1sp4, and have come across a situation that I have been unable to
          resolve. My set up is such that session ejbs send to the JMS queue (using a transacted
          QueueSessionFactory) as part of its container managed transaction. The messages
          are sent successfully (as shown in the console's monitor tab and the file store
          defined for the queue).
          However, my deployed MDB is never executed. And in fact, checking out the monitor
          tab for MDBs shows zero instances in the pool. I have not defined any pooling
          characteristics for the MDB in its deployment descriptor, and have defined it
          to be transactional using container transactions.
          Anyone have any ideas what I should look for?
          TIA
          

Answer 1

You can turn on debugging information for the MDBs so you can see what
          they're doing as they try to connect. You can do this by setting the
          following parameters when you start WLS:
          -Dweblogic.ejb20.jms.connect.debug=true
          -Dweblogic.ejb20.jms.connect.verbose=true
          You may also need to set "StdoutDebugEnabled=true" in the "Server" section
          of your config.xml file.
          This should tell you more about the deployment of your MDBs.
          greg
          "Steve Ebersole" <[email protected]> wrote in message
          news:3f42d2f8$[email protected]..
          >
          > I am using 6.1sp4, and have come across a situation that I have been
          unable to
          > resolve. My set up is such that session ejbs send to the JMS queue (using
          a transacted
          > QueueSessionFactory) as part of its container managed transaction. The
          messages
          > are sent successfully (as shown in the console's monitor tab and the file
          store
          > defined for the queue).
          >
          > However, my deployed MDB is never executed. And in fact, checking out the
          monitor
          > tab for MDBs shows zero instances in the pool. I have not defined any
          pooling
          > characteristics for the MDB in its deployment descriptor, and have defined
          it
          > to be transactional using container transactions.
          >
          > Anyone have any ideas what I should look for?
          >
          > TIA