I have also experienced this. Have you found any solutions?
Not at this stage. We don't actually need XA transaction support yet so have decided to stick with the standard config until we have more time to look into the possible casues of the performance issue. We're also hoping there will be more people using it by then which should provide more knowlegable support.
On a side note (posted for general audience) - if you're using 3.2.1 (non-XA) with optimistic locking you will also notice a drastic decrease in performance. 3.2.2 fixes this problem. Unfortuanately, currently it's only a release candidate ... we are eagerly awaiting the official release :-)
I noticed that switching from jdk1.3 to jdk1.4 caused a 100% performance degredation using the ms jdbc driver.
Have either of you experienced this? Is this a configuration issue?
Perhaps it is related to the XA performance problem you have.