MDB / application deployment

Question

          Hi,
          I am using MDB (WLS6.1/ sp-3). The MDB further delegates the processing to stateless
          session beans.
          Consider the scenario
          - Send messages to persistent Queues
          - Stop weblogic server. (Note some messages are still in queue)
          - Re-start weblogic
          - Before .ear file completely deployed, MDB starts processing the messages. It
          generates JNDI exception during lookup for stateless session bean as the application
          is not completely yet.
          Is there any way to ensure that MDB does not receive and process the messages
          unless the whole application is deployed?
          thanks
          saurabh
          

Answer 1

          As long as your mdb and session beans are packaged in the same jar, you should
          be fine. We have the same configuration(persistant queues talking to session to
          cmp). The only issue we had was the properties file which stores some startup
          options for our app was loaded only on web startup. This created a problem as
          the ejb gets loaded first and wont find those properties(The wars get deployed
          later and its the war which loads the properties). We had to put this check in
          the setmessagedriven context to see if the properties were loaded.
          HTH
          Raj
          Tom Barnes <[email protected]> wrote:
          >Hi Saurabh,
          >
          >In the past, I've heard the suggestion to programmatically deploy the
          >
          >MDB in a startup class rather than staticly deploy it. I don't
          >know the specifics. I've also seen customers simply "sleep" in the
          >MDB and retry (just make sure that the MDB pool size is smaller than
          >the
          >thread pool size to avoid consuming all threads in sleeps and locking
          >up the server.)
          >
          >I think 7.0 provides more boot ordering options (but you may need
          >to package the MDB seperately).
          >
          >I suggest posting this question to the EJB newsgroup which has
          >more experience in this area.
          >
          >Tom
          >
          >Saurabh Kumar wrote:
          >> Hi,
          >>
          >> I am using MDB (WLS6.1/ sp-3). The MDB further delegates the processing
          >to stateless
          >> session beans.
          >>
          >> Consider the scenario
          >>
          >> - Send messages to persistent Queues
          >> - Stop weblogic server. (Note some messages are still in queue)
          >> - Re-start weblogic
          >> - Before .ear file completely deployed, MDB starts processing the messages.
          >It
          >> generates JNDI exception during lookup for stateless session bean as
          >the application
          >> is not completely yet.
          >>
          >> Is there any way to ensure that MDB does not receive and process the
          >messages
          >> unless the whole application is deployed?
          >>
          >> thanks
          >> saurabh
          >>
          >>
          >