February 2017 - infinispan-issues

[JBoss JIRA] (ISPN-5654) Make DeadlockDetectingLockManager aware of single-node locking

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5654?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5654: ------------------------------- Status: Open (was: New) > Make DeadlockDetectingLockManager aware of single-node locking > -------------------------------------------------------------- > > Key: ISPN-5654 > URL: https://issues.jboss.org/browse/ISPN-5654 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 8.0.0.Beta2 > Reporter: Dan Berindei > > {{DeadlockDetectingLockManager}} seems to assume that the node that started a transaction acquires a local lock before replicating, which is wrong since we switched to locking only on the primary owner. > In particular, {{isSameKeyDeadlock}} can probably be removed altogether. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7534) Support JCache on Wildfly/EAP

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-7534?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec edited comment on ISPN-7534 at 2/28/17 4:27 AM: -------------------------------------------------------------------- As mentioned in the [JEE mailing list|https://java.net/projects/javaee-spec/lists/users/archive/2016-09/me...], JCache 1.1 is only an errata release. There will be nothing new added. So if we need new features, JCache.next is the way to go. JCache 1.1 spec might be found here: https://docs.google.com/document/d/14BvLUyv5U3zhsbIGwA4hkLfFieBkaCPfaHazh... was (Author: sebastian.laskawiec): As mentioned in the [JEE mailing list|https://java.net/projects/javaee-spec/lists/users/archive/2016-09/me...], JCache 1.1 is only an errata release. There will be nothing new added. So if we need new features, JCache.next is the way to go. > Support JCache on Wildfly/EAP > ----------------------------- > > Key: ISPN-7534 > URL: https://issues.jboss.org/browse/ISPN-7534 > Project: Infinispan > Issue Type: Feature Request > Components: Integration > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Priority: Critical > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7523) Update cached RpcOptions when timeout changes

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-7523?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-7523: ------------------------------ Status: Open (was: New) > Update cached RpcOptions when timeout changes > --------------------------------------------- > > Key: ISPN-7523 > URL: https://issues.jboss.org/browse/ISPN-7523 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Radim Vansa > Assignee: Radim Vansa > Fix For: 9.0.0.Final > > > I thought these can be safely cached, but since remote timeout can be changed at runtime, we need to listen to these changes and update cached options accordingly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7523) Update cached RpcOptions when timeout changes

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-7523?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-7523: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4897 > Update cached RpcOptions when timeout changes > --------------------------------------------- > > Key: ISPN-7523 > URL: https://issues.jboss.org/browse/ISPN-7523 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Radim Vansa > Assignee: Radim Vansa > Fix For: 9.0.0.Final > > > I thought these can be safely cached, but since remote timeout can be changed at runtime, we need to listen to these changes and update cached options accordingly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7523) Update cached RpcOptions when timeout changes

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-7523?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-7523: ------------------------------ Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.Final Resolution: Done > Update cached RpcOptions when timeout changes > --------------------------------------------- > > Key: ISPN-7523 > URL: https://issues.jboss.org/browse/ISPN-7523 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Radim Vansa > Assignee: Radim Vansa > Fix For: 9.0.0.Final > > > I thought these can be safely cached, but since remote timeout can be changed at runtime, we need to listen to these changes and update cached options accordingly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7534) Support JCache on Wildfly/EAP

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-7534?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec commented on ISPN-7534: ------------------------------------------- As mentioned in the [JEE mailing list|https://java.net/projects/javaee-spec/lists/users/archive/2016-09/me...], JCache 1.1 is only an errata release. There will be nothing new added. So if we need new features, JCache.next is the way to go. > Support JCache on Wildfly/EAP > ----------------------------- > > Key: ISPN-7534 > URL: https://issues.jboss.org/browse/ISPN-7534 > Project: Infinispan > Issue Type: Feature Request > Components: Integration > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Priority: Critical > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7534) Support JCache on Wildfly/EAP

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-7534?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec edited comment on ISPN-7534 at 2/28/17 4:13 AM: -------------------------------------------------------------------- Adam Bien created a bridge between JEE8 and JCache: https://github.com/Adopt-a-JSR/jcache-javaee A proposed [spec xml|https://github.com/Adopt-a-JSR/jcache-javaee/blob/master/jcache-javae...] looks very interesting: {code} <caches> <caching-provider>org.jsr107.ri.spi.RICachingProvider</caching-provider> <cache name="it" key="java.lang.String" value="java.lang.String"> <configuration> <property name="store.by.value" value="true"/> <property name="management.enabled" value="false"/> <property name="statistics.enabled" value="true"/> <property name="vendor.specific" value="unicorn"/> </configuration> </cache> <cache name="hack3rz" value="java.lang.String"> <configuration> <property name="store.by.value" value="false"/> <property name="management.enabled" value="true"/> <property name="statistics.enabled" value="false"/> <property name="java" value="duke"/> </configuration> </cache> </caches> {code} As mentioned in the [JEE mailing list|https://java.net/projects/javaee-spec/lists/users/archive/2016-09/me...] this is a Proof Of Concept repo. was (Author: sebastian.laskawiec): Adam Bien created a bridge between JEE8 and JCache: https://github.com/Adopt-a-JSR/jcache-javaee A proposed [spec xml|https://github.com/Adopt-a-JSR/jcache-javaee/blob/master/jcache-javae...] looks very interesting: {code} <caches> <caching-provider>org.jsr107.ri.spi.RICachingProvider</caching-provider> <cache name="it" key="java.lang.String" value="java.lang.String"> <configuration> <property name="store.by.value" value="true"/> <property name="management.enabled" value="false"/> <property name="statistics.enabled" value="true"/> <property name="vendor.specific" value="unicorn"/> </configuration> </cache> <cache name="hack3rz" value="java.lang.String"> <configuration> <property name="store.by.value" value="false"/> <property name="management.enabled" value="true"/> <property name="statistics.enabled" value="false"/> <property name="java" value="duke"/> </configuration> </cache> </caches> {code} > Support JCache on Wildfly/EAP > ----------------------------- > > Key: ISPN-7534 > URL: https://issues.jboss.org/browse/ISPN-7534 > Project: Infinispan > Issue Type: Feature Request > Components: Integration > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Priority: Critical > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7534) Support JCache on Wildfly/EAP

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-7534?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec commented on ISPN-7534: ------------------------------------------- Adam Bien created a bridge between JEE8 and JCache: https://github.com/Adopt-a-JSR/jcache-javaee A proposed [spec xml|https://github.com/Adopt-a-JSR/jcache-javaee/blob/master/jcache-javae...] looks very interesting: {code} <caches> <caching-provider>org.jsr107.ri.spi.RICachingProvider</caching-provider> <cache name="it" key="java.lang.String" value="java.lang.String"> <configuration> <property name="store.by.value" value="true"/> <property name="management.enabled" value="false"/> <property name="statistics.enabled" value="true"/> <property name="vendor.specific" value="unicorn"/> </configuration> </cache> <cache name="hack3rz" value="java.lang.String"> <configuration> <property name="store.by.value" value="false"/> <property name="management.enabled" value="true"/> <property name="statistics.enabled" value="false"/> <property name="java" value="duke"/> </configuration> </cache> </caches> {code} > Support JCache on Wildfly/EAP > ----------------------------- > > Key: ISPN-7534 > URL: https://issues.jboss.org/browse/ISPN-7534 > Project: Infinispan > Issue Type: Feature Request > Components: Integration > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Priority: Critical > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7534) Support JCache on Wildfly/EAP

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-7534?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec commented on ISPN-7534: ------------------------------------------- The JCache work is mainly driven here: * (Organization) https://github.com/jsr107 * (TCK) https://github.com/jsr107/jsr107tck * (Reference implementation) https://github.com/jsr107/RI * (Spec, Last update: Nov 21, 2016) https://github.com/jsr107/jsr107spec * (Spec web page, Last update: 2013.03.05) https://jcp.org/en/jsr/detail?id=107 > Support JCache on Wildfly/EAP > ----------------------------- > > Key: ISPN-7534 > URL: https://issues.jboss.org/browse/ISPN-7534 > Project: Infinispan > Issue Type: Feature Request > Components: Integration > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Priority: Critical > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7534) Support JCache on Wildfly/EAP

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-7534?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec commented on ISPN-7534: ------------------------------------------- There is an ongoing work on JCache.next. They are [targeting into JEE8|https://groups.google.com/forum/#!topic/jsr107/YIBGV4YQ5WY]. Top issues mentioned by Ondrej Mihalyi are: {quote} * necessary improvements to align with Java EE (we need them to bring JCache into Java EE) * optional improvements (CDI cache scope, asynchronous API, injection of Cache and CacheManager) - seems that Payara and Tomitribe already put some effort on their own, and would welcome a standard approach * integration with other specs (JPA 2nd level cache, caching JPA queries, facelet cache in JSF, JTA to span transaction over both cache and database, ...) - JCache should provide means to do it, but first JCache needs to be officially included in Java EE scope {quote} [~NadirX] added a few others: {quote} * define where container-created caches/managers are placed in JNDI so that they can be injected in applications. Because these caches could be shared among deployments, we need to think about ClassLoader issues. * define a way for a deployment to specify the caches it wants created within its lifeycle. For example JPA uses persistence.xml, CDI uses beans.xml. JCache doesn't (yet) specify a standard declarative format. * As for the Async API, we should retarget JCache to Java 8 so that we can use CompletionStage/CompletableFuture instead of coming up with our own non-standard API. {quote} Werner Keil however concluded: {quote} Just very briefly condensed it sounded like "if JCache was fit for Java EE it could be included" but looking at the rather aggressive Java EE 8 timeline, I would not expect that to happen before Java EE 9 IMHO. JTA support is just one, but certainly an important goal JCache 1.0 missed out on. Better integrating with standardized configuration (as of the new Config JSR) instead of reinventing its own configuration sub-system would be another aspect to tackle, but the Config JSR also aims at that for EE 9 mostly. {quote} > Support JCache on Wildfly/EAP > ----------------------------- > > Key: ISPN-7534 > URL: https://issues.jboss.org/browse/ISPN-7534 > Project: Infinispan > Issue Type: Feature Request > Components: Integration > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Priority: Critical > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2017