javax.jms.JMSException: Invalid transaction id.

[lolsson]

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.

Lars

[hchirino]

Do you have multiple threads using QueueSenders created from one session object???

Regards,
Hiram

[lolsson]

As far as I can tell I do not have multiple threads
using QueueSenders created from one QueueSession.

I am trying to move my app from jboss 2.4.0 to jboss 2.4.1. Currently this has given me other problems.
If I get past these and the problem with the
invalid transaction id occurs in jboss 2.4.1 as well
I will come back with more information.

Thanks,
Lars

[aglover]

Hiram,
I am extremely curious why you asked that question. If one does use QueueSenders created from one session object, does/could this cause problems? If so, why? Thanks for your insight in the matter!

[wbonnell]

I'm running 2.4.0, and I also get this exception when I send a message to a queue (with an MDB listener) though for me it happens everytime.

[wbonnell]

2.4.1 doesn't list any fixes regarding this. Do MDBs really work?

[wbonnell]

I tried connection to this queue from a stand-alone client to no avail. Now, when I attempt to create a QueueSession from the QueueConnection, I get the following JMSException:

"Cannot create a connection receiver".

I looked at the source code, and apparently it is expecting a valid clientID (whatever that is).

[hchirino]

First off, multiple threads can not share objects created from one session (per spec).

As for the the clientID thing, if you connect with a client ID, it must be valid.

[wbonnell]

Multiple threads, at least in my test code, are not the issue. And I have no idea what a client id is. However, the exception message refers to it. What am I missing?