After looking at the code it seems that connections are wrapped and if they have been opened under a transaction then they are not allowed to have the isolation level set.
Why is this?
How do you fine tune EJB methods so that their individual methods can have different isolation levels?
3.2.1 allowed you to change the isolation level...3.2.2 and upwards stops you doing any of this?
Moved to the JCA forum where it belongs.
I don't see any reason for that validation, other than it is a cut and paste error
on my part when I was fixing the continued invocations on the connection state
(which was a performance bottleneck).
I know Oracle doesn't support changing the isolation level in a transcation
but I would be happy delegating this decision to the underlying driver/db.