mdb - xa transactions

[jamoville]

I'm using jboss 3.0.7 and mdb's. I'm using the ConnectionFactory (oil) not the XAConnectionFactory and My messages have a transaction id which gets written to file in the db/jbossmq/file directory. The message itself is not written only the transaction id. Is there anyway to shut this off. I don't want all the disk io happening. Also - my mdbs are NotSupported for transactions. I've put a trace on the mq package and I can see that a SpyXAResource is being used which is causing this but I can't figure out why if I'm not using an xa connection factory.

[adrian.brock]

Your mdb is not transactional, but the
message delivery is.

In jboss.xml

<message-driven>
<ejb-name>whatever</ejb-name>
...
<session-pool-transacted>
<xa-connection>false</xa-connection>
</session-pool-transacted>
</message-driven>

This is missing from jboss_3.0.dtd

Regards,
Adrian

[jamoville]

Thanks - I added it to the jboss.xml file but it didn't change the behavior

[jamoville]

Found the problem. It was the fact that the tags should read

<session-pool-transacted>false</session-pool-transacted>
<xa-connection>false</xa-connection>