Optimistic locking + JDBC cache loader + DataSources ---------------------------------------------------- Key: JBCACHE-1408 URL: https://jira.jboss.org/jira/browse/JBCACHE-1408 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.0.0.ALPHA1, 2.2.0.GA Reporter: Mircea Markus Assignee: Manik Surtani CacheStoreInterceptor.handleCommitCommand calls CacheStoreInterceptor.storeInternalState. In the optimistic scenario, this will try to add the version of the node (internal state) to the previously stored nodes (nodes are being called in handlePrepareCommand). The problem is that handleCommitCommand is called in an transaction having the status Status.COMMITTED, and when trying to fetch a Connection, org.jboss.resource.connectionmanager.TxConnectionManager checks for current tx status and throws an exception if running tx is not active. Solution: move the code which stores additional info in handlePrepareCommand. This should also bring important performance gains, as for each node a new DB call is made in order to add the version (see CacheStoreInterceptor.storeInternalState). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira