[JBoss JIRA] Created: (ISPN-820) Resolve {@link} links in configuration reference
by Galder Zamarreño (JIRA)
Resolve {@link} links in configuration reference
-------------------------------------------------
Key: ISPN-820
URL: https://jira.jboss.org/browse/ISPN-820
Project: Infinispan
Issue Type: Feature Request
Reporter: Galder Zamarreño
Assignee: Vladimir Blagojevic
Fix For: 5.0.0.BETA1
Currently configuration reference documentation does not resolve {@link} links.
It'd be nice if it'd point to the javadoc of the corresponding class if available!
Examples:
- Fully qualified class name of a class that looks up a reference to a {@link javax.transaction.TransactionManager}. The default provided is capable of locating the default TransactionManager in most popular Java EE systems, using a JNDI lookup. (Javadoc)
- Fully qualified name of the class that the configured {@link org.infinispan.marshall.Externalizer} can marshall/unmarshall. Establishing the link between type marshalled and {@link org.infinispan.marshall.Externalizer} implementations enables users to provide their own marshalling mechanisms even for classes which they cannot modify or extend. (Javadoc)
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (ISPN-1841) Write skew checks are performed on all entries in a transaction context
by Manik Surtani (JIRA)
Manik Surtani created ISPN-1841:
-----------------------------------
Summary: Write skew checks are performed on all entries in a transaction context
Key: ISPN-1841
URL: https://issues.jboss.org/browse/ISPN-1841
Project: Infinispan
Issue Type: Bug
Components: Test Suite
Reporter: Manik Surtani
Assignee: Mircea Markus
Fix For: 5.0.2.FINAL, 5.2.0.ALPHA1
They should only be performed on entries that are read first and then updated. The current implementation doesn't cause any problems, however it is unnecessary processing and certain transactions may unnecessarily abort if, for example, an entry is read, and not written to, but the entry changes before the transaction commits.
>From Pedro Ruivo's email to infinispan-dev, where this was reported:
{quote}
I've noticed that in the last version (5.1.x) the write skew check is
performed on all keys written. However, from your documentation [1] I
understood that the write skew was meant to be performed only on the
written keys that were previously read.
Is this change intentional?
Cheers,
Pedro Ruivo
[1] https://docs.jboss.org/author/display/ISPN51/Data+Versioning
"Write skew checks are performed at prepare-time to ensure a concurrent
transaction hasn't modified an entry while it was read and potentially
updated based on the value read."
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (ISPN-1439) Async store needs redesigning to support injected executors
by Galder Zamarreño (Created) (JIRA)
Async store needs redesigning to support injected executors
-----------------------------------------------------------
Key: ISPN-1439
URL: https://issues.jboss.org/browse/ISPN-1439
Project: Infinispan
Issue Type: Enhancement
Components: Configuration, Loaders and Stores
Reporter: Galder Zamarreño
Assignee: Sanne Grinovero
Fix For: 5.2.0.FINAL
The CoalescedAsyncStore design is pretty complex and is designed around AsyncStore being able to control the lifecycle of the async store coordinator and processor executors.
A re-design of the async store is needed to enable central management of these executors, in such way that the NamedExecutorFactory can start with the right parameters (take in account that multiple caches could be configured with an async store), and the shutdown procedure can be correctly executed by the cache manager.
The async store's coalesced logic makes this a fairly complex task, particularly since the introduction of Sanne's changes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months