Liferay Portal 6.1 - User Guide
| Download PDF | Purchase Print Book |
Liferayは、コミュニティにてテクノロジーをより良く使うために役立つ豊富なリソースと知識を提供しています。
| Download PDF | Purchase Print Book |
Set the transaction isolation level for the Counter service. See transaction.isolation.portal for more information. The preferred value is 8 when the transaction manager supports it. If the transaction manager does not support it, (i.e. when using JPA and JpaTransactionManager) set this to -1 to use the database’s default isolation level.
transaction.isolation.counter=8
Set the definition of the portal transaction isolation level. The portal transaction isolation level is not a real isolation level. It is just a pointer to a real isolation level that can be configured by setting this property. Set the value to -1 to use the database’s default isolation level. Set the value to 2 to use read committed. Set the value to 1 to use read uncommitted. Set the value to 4 to use repeatable read. Set the value to 8 to use serializable.
transaction.isolation.portal=2
Set the transaction manager. It must be a class that extends org.springframework.transaction.support.AbstractPlatformTransactionManager.
The application server specific transaction managers provide XA transactions by leveraging application server specific data sources and thus require additional application server specific configuration. You should not modify this unless you know what you’re doing.
Examples:
transaction.manager.impl=org.springframework.orm.hibernate3.HibernateTransactionManager
transaction.manager.impl=org.springframework.transaction.jta.JtaTransactionManager
transaction.manager.impl=org.springframework.transaction.jta.OC4JJtaTransactionManager
transaction.manager.impl=org.springframework.transaction.jta.WebLogicJtaTransactionManager
transaction.manager.impl=org.springframework.transaction.jta.WebSphereUowTransactionManager
Additional properties that follow the pattern transaction.manager.property.\* will be read to call the setters on the transaction manager. For example, the property transaction.manager.property.globalRollbackOnParticipationFailure, will call the setter setGlobalRollbackOnParticipationFailure on the transaction manager. The list of available setters depends on the implementation specified in the property transaction.manager.impl.
allowCustomIsolationLevels should be set to true when using the JtaTransactionManager.
Examples:
transaction.manager.property.allowCustomIsolationLevels=true
transaction.manager.property.globalRollbackOnParticipationFailure=false