Invalid Transaction id JMSException in SessionBean

[philc]

Hello,

I'm getting a javax.jms.JMSException: Invalid transaction id when calling publisher.publish(message).

publish is called inside a local session bean method which was itself called by another session bean. So it's :
Session --> Session --> publish

The first session method transaction attribute is set to "RequiresNew" and the second session bean method is set to "Required".

I also checked the JMS session and getTransacted returns true. I get the connection from XAConnectionFactory like this:
(TopicConnectionFactory)jndi.lookup("XAConnectionFactory");

Should I use "java://XAConnectionFactory"? Does it matter? How can I get more info on the transaction?

Thanks,
Philippe

btw: I'm running JBoss3.0RC3


This is the exception:

javax.jms.JMSException: Invalid transaction id.
at org.jboss.mq.SpyXAResourceManager.addMessage(SpyXAResourceManager.java:71)
at org.jboss.mq.SpySession.sendMessage(SpySession.java:395)
at org.jboss.mq.SpyTopicPublisher.internalPublish(SpyTopicPublisher.java:120)
at org.jboss.mq.SpyTopicPublisher.publish(SpyTopicPublisher.java:68)
at com.brockhousecooper.tw.ejb.beans.MessengerBean.broadcastBeanFieldChanged(MessengerBean.java:138)

[philc]

I saw two changes in the JBoss3.0,1RC1 Change log. Could they be related to this problem since I'm using Oracle 9i?

# Forced ManagedConnection to always return the same XAResource as per spec by caching it, to work around non-spec compliant drivers such as Oracle.

# Create Xids through a factory (mbean), allowing easier configuration. This should make the txmanager work with any xid. The particular XidFactory supplied can be configured to produce xids of maximal size, needed by Oracle. The XidFactory interface is not well defined yet, I will fix it when we verify this works with Oracle

[philc]

You have to use JMS as a Resource (see online docs) to be able to include it in Container managed transactions.

[ygmarchi]

I tried using JMS as a Resource, but:

1) if I use the method createSession (true /* transacted */ , ..)
jboss rolls back the transaction when I close the connection.

2) if I use the method createSession (false /* not transacted */ , ..)
the transaction is non enlisted in the current one, but is only a local
transaction.

"PhilC" wrote:
You have to use JMS as a Resource (see online docs) to be able to include it in Container managed transactions.

[ygmarchi]

Also it's not clear to me why the Connection returned by a SpyXAConnectionFactory upon the invocation of createSession (true, ...), is a SpyConnection and not a SpyXAConnection.

The SPEC is clear that the method createXASession should not be used by a client, so how can I get a reference to an XAConnection?

[adrian.brock]

DO NOT HIJACK OTHER PEOPLES THREADS.

Your question is answered here:
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=43817

Regards,
Adrian