WLS 6.1 JMS Questions

Question

          A couple of questions:
          I'm using a user txn on a servlet to insert into a JMS queue, and update a field
          in the database. I'm using a Message-driven Bean (with container managed txn)
          to service said queue... When I rollback the txn in the MDB, it looks like it
          actually rolls back the servlet's txn as well! I was expecting this to result
          in the message being put back onto the queue only... Can I correct this behaviour?
          Is there a way for me (in the MDB) to take the message and place it back onto
          the queue for processing later (e.g., 5 minutes)?
          Thanks in advance, Chad
          

Answer 1

Chad Stansbury wrote:
          > A couple of questions:
          >
          > I'm using a user txn on a servlet to insert into a JMS queue, and update a field
          > in the database. I'm using a Message-driven Bean (with container managed txn)
          > to service said queue...
          > When I rollback the txn in the MDB, it looks like it
          > actually rolls back the servlet's txn as well! I was expecting this to result
          > in the message being put back onto the queue only... Can I correct this behaviour?
          You are right, this is odd and incorrect behavior, but I can't imagine
          how it happening. Contact customer support.
          >
          > Is there a way for me (in the MDB) to take the message and place it back onto
          > the queue for processing later (e.g., 5 minutes)?
          >
          There are a couple of ways. You can configure a "RedeliveryDelay" on
          the destination via the console, this delays redelivery of rolled back
          messages. Or you can commit() the transaction, and resend the message
          to its originating queue using a
          ((weblogic.jms.extensions.WLMessageProducer)producer).setTimeToDeliver(5000);
          > Thanks in advance, Chad
          Your welcome,
          Tom