3 Replies Latest reply on May 27, 2003 2:18 PM by adrian.brock

    JBOSS MQ : problem with durable messages

    ebasley

      I have 3 major problems with jboss MQ using Durable topic, jboss 3.2.1, Linux and Java 1.4.1, oracle-jbossmq-service.xml :

      1) when I send one message in the topic, I can see 17 rows in the table jms_messages for the same messageID ;

      2) When I try to redeploy the MDB, with the same subscription-id, it will receive again the same messages ! I can repeat the operation 17 times

      3) I can't send more than 6 messages per second independently of the size (same rate with HSQL), may be this is due to the first point

      Does someone has idees about those points

      Regards

      Eric

      client code :

      Context jndiContext = getInitialContext ();

      TopicConnectionFactory factory = TopicConnectionFactory)jndiContext.lookup ("ConnectionFactory");

      Topic aremTopic = (Topic)jndiContext.lookup ("topic/aremTopic");

      TopicConnection connect = factory.createTopicConnection ();
      TopicSession session = connect.createTopicSession (false,Session.AUTO_ACKNOWLEDGE);
      TopicPublisher sender = session.createPublisher (aremTopic);

      MapMessage msg = session.createMapMessage ();
      sender.publish (msg);


      Mdb deploymment file :
      <message-driven>
      <ejb-name>ExecutionReportProcessor</ejb-name>
      <destination-jndi-name>topic/aremTopic</destination-jndi-name>
      <mdb-user>guest</mdb-user>
      <mdb-passwd>guest</mdb-passwd>
      <mdb-subscription-id>ExecutionReportProcessor1</mdb-subscription-id>
      </message-driven>

      <message-driven >
      <ejb-name>ExecutionReportProcessor</ejb-name>
      <ejb-class>pm.mdb.ExecutionReportProcessorBean</ejb-class>
      <transaction-type>Container</transaction-type>

      <acknowledge-mode>Auto-acknowledge</acknowledge-mode>
      <message-driven-destination>
      <destination-type>javax.jms.Topic</destination-type>
      <subscription-durability>Durable</subscription-durability>
      </message-driven-destination>
      </message-driven >