Transaction Session, Rollback and Redelivery

Answer 1

          Well, apparently this is a bug in Weblogic 6.1 up to sp2. (I can not comment if this
          bug either exists or does not exist in 6.0 and below or 7.0 and above.) Bug ID is
          :CR080301 if this is impacting anyone else. I'll post the final outcome and if
          it gets fixed.
          (I would also ask everyone if you post a question and end up going to BEA, customer
          support, if you could post the outcome, that would make everyone's life so much easier.)
          To respond to me via E-mail, simply pull the weeds. =)
          Tom Barnes <[email protected]> wrote:
          >Hi Mike,
          >
          >As far as I know, Zach's response still stands. The behavior you are seeing,
          >given
          >the limited information posted, doesn't ring any bells. Please forward
          >your issue to
          >customer
          >support, with enough information to reproduce along with a SP number and
          >thread-dumps.
          >They will know if your particular problem has been seen before...
          >
          >If you like, post your reproducer code here, with thread-dumps.
          >
          >Tom
          >
          >P.S. Email addresses on this forum tend to be "bogus" because this is not
          >a formal
          >forum. Think of it as a free Anne Landers for JMS. Posters are volunteers,
          >posting
          >on "their own time".
          >
          >Mike Wiles wrote:
          >
          >> Was there ever any outcome to this issue? I am experiencing the same
          >behavior and
          >> since both of these E-mail addresses are pretty much bogus, it is impossible
          >to get
          >> some sort of follow-up.
          >>
          >> Mike
          >>
          >> To send me an E-mail, simply pull the WEEDS.
          >>
          >> "Zach" <[email protected]> wrote:
          >> >Very strange behavior. You should file a support case.
          >> >_sjz.
          >> >
          >> >"Bart Simpson" <[email protected]> wrote in message
          >> >news:[email protected]...
          >> >>
          >> >> Hi,
          >> >>
          >> >> I am trying to understand, how rollback works with transaction session
          >> >in
          >> >WLS
          >> >> 6.1 sp1. What should happen when session.rollback() is called? After
          >> >calling
          >> >> rollback() couple of times, the server program receiving the messages
          >> >just
          >> >hangs?
          >> >> I have configured redelivery delay to 3000 and redelivery tries to
          >3.
          >> >However,
          >> >> if I restart the server program, then I see the normal redelivery
          >> >happening again.
          >> >> Is this a feature or bug?
          >> >>
          >> >> Here is the client program:
          >> >> package com.malani.jms.client;
          >> >>
          >> >> import java.util.*;
          >> >>
          >> >> import javax.jms.*;
          >> >> import javax.naming.*;
          >> >>
          >> >> import com.malani.jms.resources.*;
          >> >>
          >> >> public class Client {
          >> >>
          >> >> public static void sendMessage(QueueSender aSender, Session aSession,
          >> >int
          >> >> i)
          >> >> throws JMSException
          >> >> {
          >> >> aSender.send(aSession.createTextMessage("" + i));
          >> >> }
          >> >>
          >> >> public static void printUsage() {
          >> >> System.out.println("Usage:");
          >> >> System.out.println(Client.class.getName() + " jndi_queue_name");
          >> >> System.exit(1);
          >> >> }
          >> >>
          >> >> public static void main(String[] args) {
          >> >> if (args.length != 1) {
          >> >> printUsage();
          >> >> }
          >> >>
          >> >> QueueSender aSender = null;
          >> >> QueueSession aSession = null;
          >> >> QueueConnection aConnection = null;
          >> >> try {
          >> >> Properties p = new Properties();
          >> >>
          >> >p.load(JMSProperties.class.getResourceAsStream("jms.properties"));
          >> >> InitialContext aIC = new InitialContext(p);
          >> >> QueueConnectionFactory aFactory = (QueueConnectionFactory)
          >> >aIC.lookup(
          >> >> p.getProperty("queue.connection.factory.name")
          >> >> );
          >> >> aConnection = aFactory.createQueueConnection();
          >> >> aConnection.start();
          >> >> aSession = aConnection.createQueueSession(
          >> >> false,
          >> >> QueueSession.AUTO_ACKNOWLEDGE
          >> >> );
          >> >> Queue aQueue = (Queue) aIC.lookup(args[0].trim());
          >> >> aSender = aSession.createSender(aQueue);
          >> >>
          >> >> int i = 0;
          >> >> for (; i < 20; i++) {
          >> >> sendMessage(aSender, aSession, i);
          >> >> }
          >> >> } catch (Exception e) {
          >> >> e.printStackTrace();
          >> >> } finally {
          >> >> try {
          >> >> if (aSender != null) {
          >> >> aSender.close();
          >> >> }
          >> >> } catch (JMSException e) {}
          >> >> try {
          >> >> if (aSession != null) {
          >> >> aSession.close();
          >> >> }
          >> >> } catch (JMSException e) {}
          >> >> try {
          >> >> if (aConnection != null) {
          >> >> aConnection.stop();
          >> >> aConnection.close();
          >> >> }
          >> >> } catch (JMSException e) {}
          >> >> }
          >> >> }
          >> >> }
          >> >>
          >> >> Here is the server program:
          >> >> package com.malani.jms.transaction;
          >> >>
          >> >> import java.util.*;
          >> >>
          >> >> import javax.jms.*;
          >> >> import javax.naming.*;
          >> >>
          >> >> import com.malani.jms.resources.*;
          >> >>
          >> >> public class Server {
          >> >> public static final String JNDI_QUEUE_NAME =
          >> >"transaction_queue_jndi_name";
          >> >>
          >> >> public static void main(String[] args) {
          >> >> QueueReceiver aReceiver = null;
          >> >> QueueSession aSession = null;
          >> >> QueueConnection aConnection = null;
          >> >> try {
          >> >> Properties p = new Properties();
          >> >>
          >> >p.load(JMSProperties.class.getResourceAsStream("jms.properties"));
          >> >> InitialContext aIC = new InitialContext(p);
          >> >> QueueConnectionFactory aFactory = (QueueConnectionFactory)
          >> >aIC.lookup(
          >> >> p.getProperty("queue.connection.factory.name")
          >> >> );
          >> >> aConnection = aFactory.createQueueConnection();
          >> >> aConnection.start();
          >> >> aSession = aConnection.createQueueSession(
          >> >> true,
          >> >> -1 // doesn't really matter
          >> >> );
          >> >> Queue aQueue = (Queue) aIC.lookup(JNDI_QUEUE_NAME);
          >> >> aReceiver = aSession.createReceiver(aQueue);
          >> >> final QueueSession aQS = aSession;
          >> >> MessageListener aML = new MessageListener() {
          >> >> public void onMessage(Message m) {
          >> >> try {
          >> >> TextMessage aTM = (TextMessage) m;
          >> >> String s = aTM.getText();
          >> >> System.out.println("Text is:\t" + s);
          >> >> int i = Integer.parseInt(s);
          >> >> if (i < 15) {
          >> >> aQS.commit();
          >> >> } else {
          >> >> aQS.rollback();
          >> >> }
          >> >> } catch (JMSException e) {
          >> >> e.printStackTrace();
          >> >> }
          >> >> }
          >> >> };
          >> >> aReceiver.setMessageListener(aML);
          >> >> byte[] b = new byte[1];
          >> >> System.in.read(b);
          >> >> } catch (Exception e) {
          >> >> e.printStackTrace();
          >> >> } finally {
          >> >> try {
          >> >> if (aReceiver != null) {
          >> >> aReceiver.close();
          >> >> }
          >> >> } catch (JMSException e) {}
          >> >> try {
          >> >> if (aSession != null) {
          >> >> aSession.close();
          >> >> }
          >> >> } catch (JMSException e) {}
          >> >> try {
          >> >> if (aConnection != null) {
          >> >> aConnection.stop();
          >> >> aConnection.close();
          >> >> }
          >> >> } catch (JMSException e) {}
          >> >> }
          >> >> }
          >> >> }
          >> >>
          >> >> Here is the properties file:
          >> >> #
          >> >> java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory
          >> >> java.naming.provider.url=t3://localhost:7001
          >> >> queue.connection.factory.name=weblogic.jms.ConnectionFactory
          >> >>
          >> >#queue.connection.factory.name=weblogic.jms.MessageDrivenBeanConnectionFacto
          >> >ry
          >> >> #queue.connection.factory.name=transaction_connection_factory_jndi_name
          >> >>
          >> >> Here is the JMSProperties file:
          >> >> package com.malani.jms.resources;
          >> >>
          >> >> public class JMSProperties {
          >> >> }
          >> >>
          >> >> The first time the server is run, it hangs at 16. Messages 17, 18,
          >and
          >> >19
          >> >are
          >> >> not processed. Is this correct behavior:
          >> >> Text is: 0
          >> >>
          >> >> Text is: 1
          >> >>
          >> >> Text is: 2
          >> >>
          >> >> Text is: 3
          >> >>
          >> >> Text is: 4
          >> >>
          >> >> Text is: 5
          >> >>
          >> >> Text is: 6
          >> >>
          >> >> Text is: 7
          >> >>
          >> >> Text is: 8
          >> >>
          >> >> Text is: 9
          >> >>
          >> >> Text is: 10
          >> >>
          >> >> Text is: 11
          >> >>
          >> >> Text is: 12
          >> >>
          >> >> Text is: 13
          >> >>
          >> >> Text is: 14
          >> >>
          >> >> Text is: 15
          >> >>
          >> >> Text is: 16
          >> >>
          >> >>
          >> >> What happened to message 17, 18, and 19?
          >> >>
          >> >> Now, if I stop the server, and start it again, I see the requequing
          >and
          >> >redelivery
          >> >> of the messages as shown below:
          >> >> Text is: 15
          >> >>
          >> >> Text is: 16
          >> >>
          >> >> Text is: 17
          >> >>
          >> >> Text is: 18
          >> >>
          >> >> Text is: 19
          >> >>
          >> >> Text is: 15
          >> >>
          >> >> Text is: 17
          >> >>
          >> >> Text is: 16
          >> >>
          >> >> Text is: 18
          >> >>
          >> >> Text is: 19
          >> >>
          >> >> Text is: 15
          >> >>
          >> >> Text is: 17
          >> >>
          >> >> Text is: 16
          >> >>
          >> >> Text is: 18
          >> >>
          >> >> Text is: 19
          >> >>
          >> >> Text is: 17
          >> >>
          >> >> Text is: 18
          >> >>
          >> >> Text is: 19
          >> >>
          >> >>
          >> >> Is there some optimization going on?
          >> >>
          >> >> Thank you so much....
          >> >>
          >> >>
          >> >
          >> >
          >