Why startTx & commit if MDB transaction=NotSupported?

[jhaddad]

I'm looking at my MDB performance using a cpu profiler. I see quite a few calls being made pertaining to transactions (e.g. SpyXAResource.Manager.startTx, SpyXAResource.commit, etc.).

I'm confused because my MDB is deployed to be non-transactional.

These invocations don't take up a whole lot of cpu, but I'm trying to trim off every unnecessary tick possible, as my CPU is pinned at 100%.

Thanks.

[adrian.brock]

Message delivery is still transactional even when the tx is suspended
for your mdb (non-transacted).