8 Replies Latest reply on Sep 25, 2001 10:51 AM by William Bonnell

    javax.jms.JMSException: Invalid transaction id.

    Lars Olsson Newbie

      I have a message driven bean that acts as a filter.
      It consumes data items from one queue, transforms them,
      and writes the transformed values to another queue.

      The bean uses container managed transactions.

      This works most of the time, but every now and then
      the following appears in the jboss window:

      [s2] javax.jms.JMSException: Invalid transaction id.
      [s2] at org.jbossmq.SpyXAResourceManager.addMessage(SpyXAResourceManager.java:80)
      [s2] at org.jbossmq.SpySession.sendMessage(SpySession.java:360)
      [s2] at org.jbossmq.SpyQueueSender.send(SpyQueueSender.java:103)
      [s2] at org.jbossmq.SpyQueueSender.send(SpyQueueSender.java:62)

      Any ideas about what I might have done
      wrong to get this behaviour?

      The queue that the bean writes to is also being
      written to by another bean. Can JMS destinations have
      multiple writers?

      I am using JBOSS 2.4.0 on Red Hat Linux 6.2.