2 Replies Latest reply on Apr 18, 2007 8:28 AM by Weston M. Price

    Msg expiration doesn't work with a msg listener on a session

    Carlo de Wolf Master

      The JCA uses session.setMessageListener which creates a SpyMessageConsumer with sessionConsumer = true.
      Messages are received and added to the SpyMessageConsumer (addMessage).
      If it's a sessionConsumer do special logic (excluding expiration) else put it on queue and receive() does expiration logic.

      I've create a unit test in org.jboss.test.jbossmq.test.JBAS4328TestCase. Can I re-open the issue?

      Either it's a bug in JBossMQ or a semantic error in use of JBossMQ. I still vote for the former, because when the message leaves MQ it has an inproper invariant (message expired (with more than ~100ms)).