Problem with TopicConnection.createDurableConnectionConsumer

Question

Hi, we are using Weblogic 6.1 sp 2 under Linux and we are having problems
          when trying to create durable consummers, the problem is tat, even when it
          doesn't seems to be any problem when creating them they don't receive
          messages sended to the topics they are subscribed. We can see the messages
          getting hold onto the message queue.
          Here is the code of a function we use to subscribe our consummers:
          TopicConnectionFactory tconFactory;
          TopicConnection tcon;
          TopicSession tsession;
          Topic topic;
          ServerSessionPool sessionPool;
          ConnectionConsumer consumer;
          String connectionFactory = (String)args.get("connectionFactory");
          String topicName = (String)args.get("topic");
          String action = (String)args.get("action");
          String name = (String)args.get("name");
          String persistence = "";
          String selector = "";
          int maxsessions = 1; // 1 by default
          int maxmessages = 1; // 1 by default
          if (args.get("selector") != null)
          selector = (String)args.get("selector");
          if (args.get("persistence") != null)
          persistence = (String)args.get("persistence");
          if (args.get("maxsessions") != null)
          maxsessions = Integer.parseInt((String)args.get("maxsessions"));
          if (args.get("maxmessages") != null)
          maxmessages = Integer.parseInt((String)args.get("maxmessages"));
          if (connectionFactory == null || topicName == null)
          throw new IllegalArgumentException("connectionFactory=" +
          connectionFactory + ", topicName=" + topicName);
          try
          tconFactory = (TopicConnectionFactory) ctx.lookup(connectionFactory);
          tcon = tconFactory.createTopicConnection();
          tcon.setClientID(topicName + ++uqTopicID);
          tsession = tcon.createTopicSession(false, Session.AUTO_ACKNOWLEDGE);
          topic = (Topic) ctx.lookup(topicName);
          tcon.start();
          sessionPool =
          sessionPoolFactory.getServerSessionPool(tcon,maxsessions,false,Session.AUTO_
          ACKNOWLEDGE,name);
          if (!selector.equals(""))
          if (persistence.equals("Y"))
          consumer = tcon.createDurableConnectionConsumer(topic, name ,
          selector, sessionPool, maxmessages);
          else
          consumer = tcon.createConnectionConsumer(topic, selector, sessionPool,
          maxmensajes);
          catch (NamingException ne)
          ne.printStackTrace();
          catch (javax.jms.JMSException jmse)
          jmse.printStackTrace();
          of course this is just the code of a function we call from a loop in order
          to make the subscriptions.
          As you can see in this part of the code:
          if (persistence.equals("Y"))
          consumer = tcon.createDurableConnectionConsumer(topic, name ,
          selector, sessionPool, maxmessages);
          else
          consumer = tcon.createConnectionConsumer(topic, selector, sessionPool,
          maxmensajes);
          we use a variable in order to make the subscription durable or not. The
          problem is that all the subscriptions that are not durable are getting the
          messages but the durable ones don't.
          We don't really know in any case what the second parameter (name) on the
          createDurableConnectionConsumer method should contain, we have tried with
          the client ID we set to the TopicConnection a few lines above but still
          doesn't work.
          Are we doing something wrong?
          I have readed another post in this newsgroup from Alex Lui asking a similar
          question:
          <quote>
          Alex Lui
          Wednesday, 29 May 2002 4:59
          weblogic.developer.interest.jms
          TopicConnection.createDurableConnectionConsumer
          According to 7.0 documentation, this operation is still not supported. Is
          there any plan which release will support it?
          </quote>
          then, Tom Barnes answers him:
          <quote>
          Tom Barnes
          Wednesday, 29 May 2002 21:42
          weblogic.developer.interest.jms
          Re: TopicConnection.createDurableConnectionConsumer
          Nothing planned in near term (that I know of). This is not a J2EE
          requirement.
          Contact BEA customer support and put in an enhancement request if this is
          important to you. Meanwhile, use an MDB with a durable subscriber. For
          almost all use cases, MDBs are more apable than connection consumers.
          Tom
          </quote>
          We do really need to subscribe a "class" instead of an instance of an object
          in order to process messages concurrently.
          If our aproach is not feasible, what would be the right one?
          Notice that we are not using MDBs as we are currently using EJB 1.1
          specification. Would it be possible to use both EJB 1.0 and EJB 2.0 at the
          same time by packaging them into two .jar files earch one having a different
          ejb-jar.xml and weblogic-ejb-jar.xml files for each one with different EJB
          versions? Will it be possible then to call EJB 1.0 beans from the MDB 2.0
          subscribers?
          Thanks in advance
          Regards,
          Ignacio G. Dupont.
          

Answer 1

You are correct, durable connection consumers are not supported.
          A work around would be to use the weblogic messaging bridge (available
          in SP3), to forward a standard durable subscription into some queue, and
          then put your consumer on that.
          As for mixing EJB 1.0 and EJB 2.0 in order to use MDBs, I do not know what
          the issues might be. I suspect there aren't any. Try posting your question to
          the weblogic.developer.interest.ejb newsgroup.
          Tom
          "Ignacio G. Dupont" wrote:
          > Hi, we are using Weblogic 6.1 sp 2 under Linux and we are having problems
          > when trying to create durable consummers, the problem is tat, even when it
          > doesn't seems to be any problem when creating them they don't receive
          > messages sended to the topics they are subscribed. We can see the messages
          > getting hold onto the message queue.
          >
          > Here is the code of a function we use to subscribe our consummers:
          >
          > TopicConnectionFactory tconFactory;
          > TopicConnection tcon;
          > TopicSession tsession;
          > Topic topic;
          > ServerSessionPool sessionPool;
          > ConnectionConsumer consumer;
          >
          > String connectionFactory = (String)args.get("connectionFactory");
          > String topicName = (String)args.get("topic");
          > String action = (String)args.get("action");
          > String name = (String)args.get("name");
          > String persistence = "";
          > String selector = "";
          > int maxsessions = 1; // 1 by default
          > int maxmessages = 1; // 1 by default
          >
          > if (args.get("selector") != null)
          > selector = (String)args.get("selector");
          > if (args.get("persistence") != null)
          > persistence = (String)args.get("persistence");
          > if (args.get("maxsessions") != null)
          > maxsessions = Integer.parseInt((String)args.get("maxsessions"));
          > if (args.get("maxmessages") != null)
          > maxmessages = Integer.parseInt((String)args.get("maxmessages"));
          >
          > if (connectionFactory == null || topicName == null)
          > {
          > throw new IllegalArgumentException("connectionFactory=" +
          > connectionFactory + ", topicName=" + topicName);
          > }
          > try
          > {
          > tconFactory = (TopicConnectionFactory) ctx.lookup(connectionFactory);
          > tcon = tconFactory.createTopicConnection();
          > tcon.setClientID(topicName + ++uqTopicID);
          > tsession = tcon.createTopicSession(false, Session.AUTO_ACKNOWLEDGE);
          > topic = (Topic) ctx.lookup(topicName);
          > tcon.start();
          >
          > sessionPool =
          > sessionPoolFactory.getServerSessionPool(tcon,maxsessions,false,Session.AUTO_
          > ACKNOWLEDGE,name);
          >
          > if (!selector.equals(""))
          > {
          > if (persistence.equals("Y"))
          > consumer = tcon.createDurableConnectionConsumer(topic, name ,
          > selector, sessionPool, maxmessages);
          > else
          > consumer = tcon.createConnectionConsumer(topic, selector, sessionPool,
          > maxmensajes);
          > }
          > }
          > catch (NamingException ne)
          > {
          > ne.printStackTrace();
          > }
          > catch (javax.jms.JMSException jmse)
          > {
          > jmse.printStackTrace();
          > }
          >
          > of course this is just the code of a function we call from a loop in order
          > to make the subscriptions.
          >
          > As you can see in this part of the code:
          >
          > if (persistence.equals("Y"))
          > consumer = tcon.createDurableConnectionConsumer(topic, name ,
          > selector, sessionPool, maxmessages);
          > else
          > consumer = tcon.createConnectionConsumer(topic, selector, sessionPool,
          > maxmensajes);
          >
          > we use a variable in order to make the subscription durable or not. The
          > problem is that all the subscriptions that are not durable are getting the
          > messages but the durable ones don't.
          >
          > We don't really know in any case what the second parameter (name) on the
          > createDurableConnectionConsumer method should contain, we have tried with
          > the client ID we set to the TopicConnection a few lines above but still
          > doesn't work.
          >
          > Are we doing something wrong?
          >
          > I have readed another post in this newsgroup from Alex Lui asking a similar
          > question:
          >
          > <quote>
          >
          > Alex Lui
          > Wednesday, 29 May 2002 4:59
          > weblogic.developer.interest.jms
          > TopicConnection.createDurableConnectionConsumer
          >
          > According to 7.0 documentation, this operation is still not supported. Is
          > there any plan which release will support it?
          >
          > </quote>
          >
          > then, Tom Barnes answers him:
          >
          > <quote>
          >
          > Tom Barnes
          > Wednesday, 29 May 2002 21:42
          > weblogic.developer.interest.jms
          > Re: TopicConnection.createDurableConnectionConsumer
          >
          > Nothing planned in near term (that I know of). This is not a J2EE
          > requirement.
          > Contact BEA customer support and put in an enhancement request if this is
          > important to you. Meanwhile, use an MDB with a durable subscriber. For
          > almost all use cases, MDBs are more apable than connection consumers.
          >
          > Tom
          >
          > </quote>
          >
          > We do really need to subscribe a "class" instead of an instance of an object
          > in order to process messages concurrently.
          >
          > If our aproach is not feasible, what would be the right one?
          >
          > Notice that we are not using MDBs as we are currently using EJB 1.1
          > specification. Would it be possible to use both EJB 1.0 and EJB 2.0 at the
          > same time by packaging them into two .jar files earch one having a different
          > ejb-jar.xml and weblogic-ejb-jar.xml files for each one with different EJB
          > versions? Will it be possible then to call EJB 1.0 beans from the MDB 2.0
          > subscribers?
          >
          > Thanks in advance
          >
          > Regards,
          >
          > Ignacio G. Dupont.