Loading...

XML

Word

Printable

Feedback Policy:

We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

We should switch confluence to using per-session level transaction isolation, rather than relying on customers modifying the global setting.

Some customers can't (or are unwilling to) change the default settings for isolation globally for their MySQL. We need to provide a better solution for these customers, and to reduce the configuration effort for all customers. Using per session isolation settings (via hibernate.connection.isolation=2, see http://docs.jboss.org/hibernate/core/3.3/reference/en/html/session-configuration.html#configuration-optional and http://download.oracle.com/javase/6/docs/api/constant-values.html#java.sql.Connection.TRANSACTION_READ_COMMITTED) would fit the bill nicely.

has a derivative of

CONFSERVER-22641 Automatically upgrade session isolation transaction levels to READ-COMMITTED for MySQL

incorporates

CONFSERVER-29805 Documentation upgrade - Confluence mysql database configuration

is blocked by

CONFSERVER-22073 Transaction isolation override in confluence.cfg.xml does not apply to bootstrap checks

is related to

CONFSERVER-23057 Verify MySQL isolation level check with datasource config

relates to

CONFSERVER-22800 MySQL isolation level check does not work for JNDI datasources