[JBoss JIRA] (ISPN-3048) Eviction needs to be transactional
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-3048?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-3048:
--------------------------------
Fix Version/s: 5.3.0.Beta1
5.3.0.Final
> Eviction needs to be transactional
> ----------------------------------
>
> Key: ISPN-3048
> URL: https://issues.jboss.org/browse/ISPN-3048
> Project: Infinispan
> Issue Type: Bug
> Components: Eviction
> Affects Versions: 5.3.0.Alpha1
> Reporter: Paul Ferraro
> Assignee: Dan Berindei
> Priority: Critical
> Fix For: 5.3.0.Beta1, 5.3.0.Final
>
>
> Currently, Infinispan eviction is non-transactional. This makes Infinispan's eviction manager virtually unusable, since non-transactional eviction can cause phantom reads and data loss because it violates the isolation of concurrent transactions. This is especially problematic when using a passivation-enabled cache store. In this case, a cache eviction/passivation can cause a concurrently executed cache retrieval to return null - even though the act of passivation does not change the data - it only changes where it is stored.
> We work around this in the AS by performing eviction manually, using pessimistic locking in combination with eager lock acquisition prior to eviction. This is unfortunate, since it prevents me from leveraging Infinispan's build-in eviction strategies.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (ISPN-3055) Unreleased lock after node restart
by Deyan Pandulev (JIRA)
[ https://issues.jboss.org/browse/ISPN-3055?page=com.atlassian.jira.plugin.... ]
Deyan Pandulev updated ISPN-3055:
---------------------------------
Description:
Using dummy transaction manager I was able to produce locks that are not released. The same behavior can be reproduced with Glassfish AS 3.1.1 using its own TM.
was:
Using dummy transaction manager I was able to produce locks that are not released.
> Unreleased lock after node restart
> ----------------------------------
>
> Key: ISPN-3055
> URL: https://issues.jboss.org/browse/ISPN-3055
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 5.2.1.Final
> Environment: Debian Squeeze Amd 64, JDK 1.6.0_32
> Reporter: Deyan Pandulev
> Assignee: Mircea Markus
> Attachments: SimpleClusterRead.java, SimpleClusterWriter.java, simple_cluster_node1.xml, simple_cluster_node2.xml
>
>
> Using dummy transaction manager I was able to produce locks that are not released. The same behavior can be reproduced with Glassfish AS 3.1.1 using its own TM.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (ISPN-3055) Unreleased lock after node restart
by Deyan Pandulev (JIRA)
[ https://issues.jboss.org/browse/ISPN-3055?page=com.atlassian.jira.plugin.... ]
Deyan Pandulev updated ISPN-3055:
---------------------------------
Attachment: SimpleClusterRead.java
SimpleClusterWriter.java
simple_cluster_node1.xml
simple_cluster_node2.xml
> Unreleased lock after node restart
> ----------------------------------
>
> Key: ISPN-3055
> URL: https://issues.jboss.org/browse/ISPN-3055
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 5.2.1.Final
> Environment: Debian Squeeze Amd 64, JDK 1.6.0_32
> Reporter: Deyan Pandulev
> Assignee: Mircea Markus
> Attachments: SimpleClusterRead.java, SimpleClusterWriter.java, simple_cluster_node1.xml, simple_cluster_node2.xml
>
>
> Using dummy transaction manager I was able to produce locks that are not released.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (ISPN-3055) Unreleased lock after node restart
by Deyan Pandulev (JIRA)
Deyan Pandulev created ISPN-3055:
------------------------------------
Summary: Unreleased lock after node restart
Key: ISPN-3055
URL: https://issues.jboss.org/browse/ISPN-3055
Project: Infinispan
Issue Type: Bug
Affects Versions: 5.2.1.Final
Environment: Debian Squeeze Amd 64, JDK 1.6.0_32
Reporter: Deyan Pandulev
Assignee: Mircea Markus
Using dummy transaction manager I was able to produce locks that are not released.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (ISPN-470) Native Hot Rod client for C++
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-470?page=com.atlassian.jira.plugin.s... ]
Mircea Markus updated ISPN-470:
-------------------------------
Environment:
Minimal: Windows, 64-bit, Visual Studio 2010* RHEL 6, 64-bit
Optional: RHEL 5, 64-bit
was:
Minimal: Windows, 64-bit, Visual Studio 2010* RHEL 6, 64-bit
Optional: Windows, 32-bit, Visual Studio 2010* RHEL 5, 64-bit
> Native Hot Rod client for C++
> -----------------------------
>
> Key: ISPN-470
> URL: https://issues.jboss.org/browse/ISPN-470
> Project: Infinispan
> Issue Type: Feature Request
> Components: Remote protocols
> Environment: Minimal: Windows, 64-bit, Visual Studio 2010* RHEL 6, 64-bit
> Optional: RHEL 5, 64-bit
> Reporter: Manik Surtani
> Fix For: 6.0.0.Final
>
>
> C++ client impl for HotRod. Protocol is documented here:
> http://community.jboss.org/wiki/HotRodProtocol
> Could be based off the Java reference impl client:
> https://github.com/infinispan/infinispan/tree/master/client/hotrod-client
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (ISPN-3054) Add ability to customize the creation of Work instances in QueryInterceptor
by Marko Lukša (JIRA)
Marko Lukša created ISPN-3054:
---------------------------------
Summary: Add ability to customize the creation of Work instances in QueryInterceptor
Key: ISPN-3054
URL: https://issues.jboss.org/browse/ISPN-3054
Project: Infinispan
Issue Type: Enhancement
Components: Querying
Reporter: Marko Lukša
Assignee: Marko Lukša
CapeDwarf needs a way to index a cache entry into multiple indexes. We can achieve this with index sharding and sending multiple Work instances for a given cache entry to Hibernate-Search.
Currently, QueryInterceptor simply creates a single Work object. We need this to be able to override this and create multiple Work objects.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (ISPN-3053) Enhance JCache documentation
by Galder Zamarreño (JIRA)
Galder Zamarreño created ISPN-3053:
--------------------------------------
Summary: Enhance JCache documentation
Key: ISPN-3053
URL: https://issues.jboss.org/browse/ISPN-3053
Project: Infinispan
Issue Type: Task
Components: JCache
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.3.0.Final
Add documentation on:
- Expiration
- JCache annotations (bring it from the CDI page?)
- Transactions
- invokeEntryProcessor operation
- Cache listeners
- How to use JCache can be used without Maven
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (ISPN-3052) Upgrade aesh to 0.33.1
by Tristan Tarrant (JIRA)
Tristan Tarrant created ISPN-3052:
-------------------------------------
Summary: Upgrade aesh to 0.33.1
Key: ISPN-3052
URL: https://issues.jboss.org/browse/ISPN-3052
Project: Infinispan
Issue Type: Component Upgrade
Components: CLI
Affects Versions: 5.3.0.Alpha1
Reporter: Tristan Tarrant
Assignee: Tristan Tarrant
Fix For: 5.3.0.Beta1
Currently the Infinispan Server shell breaks because it requires this more recent version
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years