[
http://jira.jboss.com/jira/browse/JBCACHE-991?page=all ]
Manik Surtani updated JBCACHE-991:
----------------------------------
Assignee: Mircea Markus (was: Manik Surtani)
Non-JTA based mechanism for batching invocations
------------------------------------------------
Key: JBCACHE-991
URL:
http://jira.jboss.com/jira/browse/JBCACHE-991
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Brian Stansberry
Assigned To: Mircea Markus
Fix For: 3.0.0
Currently JBC uses the lifecycle of a JTA Transaction to scope a series of cache
invocations doing things like lock release, replication and cache loader storage as part
of the transaction commit. Need a mechanism to do this kind of invocation batching that
doesn't depend on JTA. Needed to allow callers that don't wish their work to be
associated with an active JTA transaction to still get the batching behavior JBC
provides.
AS web session replication is an example use case. It uses BatchModeTransactionManger to
ensure its activity doesn't impact any ongoing transaction. But
BatchModeTransactionManager isn't a good JTA transaction manager even though it
implements the JTA interfaces. So using it is problematic; it can easily be misused by
those who don't understand it's limitations (e.g. hooking it up to a JTA
Datasource.)
A couple of possible approaches have been discussed:
1) A new API added to Cache. Methods like startBatch(), commitBatch(), rollbackBatch(),
along with some internal mechanism to timeout a batch that's been started but never
committed/rolled-back.
2) Abstract away the JTA API such that JBC doesn't use JTA directly, but rather its
own interfaces that largely parallel TransactionManager and Transaction. Provide an impl
that simply wraps a real JTA TransactionManager. BatchModeTransactionManger would be
another impl. API includes a method like 'boolean isJTACompliant()' that things
like CacheLoader impls can check at startup to confirm they are working with a compatible
impl (e.g. if JBDCCacheLoader is configured to use a JTA Datasource but isJTACompliant()
returns false, throw an exception at startup.)
Apologies if this is a duplicate issue. Thought there was something like this but
couldn't find it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira