Though I manage my pooled connections and transaction isolation level from jBoss datasource configuration, I see that Modeshape code still calls setTransactionIsolation method on the connection object. This is redundant call and unnecessary round trip to DB server as it is already set by the pool. Under load the call adds more time to the performance as well. The better way to handle this is to first check getTransactionIsolation on the connection and if it is not set, then call the method. The two class files where it is being called is DataSourceManager and DatabaseBinaryStore. Any alternatives to suppress this call through Modeshape configuration?
