Message Redelivery

Question

          Hi there,
          I would like to know how to set the JMS Message Redelivery from a server restart
          to only redeliver message after all the weblogic startup classes have completed?
          The reason for this is because the message consumer(s) depend on some configuration
          setting that are setup by the startup classes and I am getting problems during a
          server restart because the container is trying to redeliver the persisted message
          BEFORE the startup classes have completed there execution.
          Thanks!
          Vincent
          

Answer 1

Another approach would be to have your startup class spawn it's own thread
          (that contains code to deploy your MDB application) and do a JMX call to
          query if the server is up and listening (meaning that all services have been
          deployed). The JMX call could be in a loop with a sleep interval. Once the
          server is up the thread can deploy your MDBs. This way you don't have to
          worry about your MDBs consuming all available threads.
          To deploy the application using JMX, you could use code like the below. The
          following code also makes sure that the config.xml is not updated so that
          you can achieve a custom deploy every time your server is re-cycled.
          public class ApplicationDeployer implements Runnable {
          private MBeanHome home;
          private TargetMBean targetMBean;
          private ApplicationMBean appMBean;
          private WebLogicObjectName targetObj;
          .... include methods to start the thread and check if the server is up
          public void doDeploy() {
          ComponentMBean deployBean = null;
          try
          ApplicationMBean appMBean = (ApplicationMBean)
          home.findOrCreateAdminMBean(appName, "Application", domainName);
          appMBean.setPath(appPath);
          if (deployFileName.indexOf(".jar")>0){
          deployBean = (EJBComponentMBean)
          home.createAdminMBean( deployAppName ,
          "EJBComponent", domainName, appMBean);
          } else if (deployFileName.indexOf(".war")>0){
          deployBean = (WebAppComponentMBean)
          home.createAdminMBean( deployAppName ,
          "WebAppComponent", domainName, appMBean);
          if ( Double.valueOf(getVersion()).doubleValue() > 6.0 )
          deployBean.setPersistenceEnabled( false );
          deployBean.setURI(deployFileName);
          deployBean.addTarget(targetMBean);
          appMBean.addComponent(deployBean);
          appMBean.deploy();
          appMBean.load();
          catch (Exception e){
          System.err.println("Exception at AppDeployer.doDeploy " , e);
          Thanks,
          Adarsh
          "Tom Barnes" <[email protected]> wrote in message
          news:[email protected]...
          > The messages on boot are not "redelivered" messages (there is no matching
          > recover/rollback in the current server's context), so a delay has no
          effect.
          > I'm sorry if I gave the impression that a redelivery delay has an effect
          at boot time...
          > Specifically, redelivery delay configures the amount of time a message
          should remain
          > in limbo before it is made visible again after an application calls
          recover or rollback.
          >
          > You really should post to the ejb newsgroup. I think there may be some
          control
          > over startup ordering (MDB after startup classes).
          >
          > Worse comes to worse, your MDB
          > can block (wait()) until the startup class calls notify() - Just make sure
          the MDBs max
          > pool size is less than the default-thread-pool-size, or make sure to
          give the MDBs
          > their own thread pool, to prevent them from consuming all available
          threads.
          >
          > Tom
          > Vincent wrote:
          >
          > > Hi Tom,
          > >
          > > I am using WLS6.1 sp2 running on solaris. The problem I am having is
          that messages
          > > are getting reloaded and sent at the next server restart before my
          weblogic startup
          > > class has completed its execution. My onMessage() method in my
          MDB(shouldn't matter
          > > if it's a MDB or a PTP JMS consumer..?) depends on some objects that are
          initialized
          > > by the startup class. I tried setting DefaultRedeliveryDelay in the
          JMSConnectionFactory
          > > to a very long delay but that does not help.
          > >
          > > Tom Barnes <[email protected]> wrote:
          > > >By "containers" I assume you mean MDBs???? Please post your question
          to
          > > >the ejb newsgroup, along with your version and SP level.
          > > >
          > > >Tom
          > > >
          >