August 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9876) Commons and embedded feature-packs should utilise 1.3 schema for backwards-compatibility

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9876?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9876: ---------------------------------- Sprint: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33 (was: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32) > Commons and embedded feature-packs should utilise 1.3 schema for backwards-compatibility > -------------------------------------------------------------------------------------------- > > Key: ISPN-9876 > URL: https://issues.jboss.org/browse/ISPN-9876 > Project: Infinispan > Issue Type: Bug > Components: WildFly modules > Affects Versions: 10.0.0.Alpha2, 9.4.5.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Alpha3, 9.4.6.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9877) Nashorn and sun.scription modules optional for embedded feature-packs

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9877?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9877: ---------------------------------- Sprint: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33 (was: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32) > Nashorn and sun.scription modules optional for embedded feature-packs > --------------------------------------------------------------------- > > Key: ISPN-9877 > URL: https://issues.jboss.org/browse/ISPN-9877 > Project: Infinispan > Issue Type: Bug > Components: WildFly modules > Affects Versions: 10.0.0.Alpha2, 9.4.5.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Alpha3, 9.4.6.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9915) JDBC publish Flowable should explicitly rollback connection

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9915?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9915: ---------------------------------- Sprint: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33 (was: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32) > JDBC publish Flowable should explicitly rollback connection > ----------------------------------------------------------- > > Key: ISPN-9915 > URL: https://issues.jboss.org/browse/ISPN-9915 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 10.0.0.Alpha3, 9.4.6.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 9.4.7.Final, 10.0.0.Beta1 > > > The Flowable for the JDBC store publisher sets `autoCommit(false)` in order for pagination to work as expected, however we never explicitly call commit or rollback on the connection, therefore the exact behaviour is determined by the underlying connection pool. Instead we should explicitly call rollback() on the connection after the publisher has finished, because the operation is read only. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9905) Rest store should retrieve created and lastUsed TS from server

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9905?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9905: ---------------------------------- Sprint: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33 (was: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32) > Rest store should retrieve created and lastUsed TS from server > -------------------------------------------------------------- > > Key: ISPN-9905 > URL: https://issues.jboss.org/browse/ISPN-9905 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores, REST > Affects Versions: 10.0.0.Alpha2 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta1 > > > Currently the rest store simply sets the created and lastUsed entries to the current time of the node loading an entry, instead we should retrieve this value from the server if fetchMetadata is true. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9932) Avoid creating MarshallableEntry instances if no CacheWriter enabled

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9932?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9932: ---------------------------------- Sprint: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33 (was: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32) > Avoid creating MarshallableEntry instances if no CacheWriter enabled > -------------------------------------------------------------------- > > Key: ISPN-9932 > URL: https://issues.jboss.org/browse/ISPN-9932 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Affects Versions: 10.0.0.Alpha3 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta1 > > > The (Dist)CacheWriterIntercepter is enabled if any loader/store is configured. The problem, is that the interceptor assumes that a CacheWriter is always configured. However, it is possible that only a CacheLoader has been configured, in which case when a write command visits the interceptor, MarshallableEntry instances are created unnecessarily in order to call the various PersistenceManager write operations. > To avoid unnecessary allocations and the marshalling of key/value/metadata that is never stored, we should ensure that calls to PersistenceManager write methods are only called if a CacheWriter is actually configured. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9962) Feature-packs should optionally depend on jdk-unsupported and sun.jdk

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9962?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9962: ---------------------------------- Sprint: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33 (was: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32) > Feature-packs should optionally depend on jdk-unsupported and sun.jdk > --------------------------------------------------------------------- > > Key: ISPN-9962 > URL: https://issues.jboss.org/browse/ISPN-9962 > Project: Infinispan > Issue Type: Bug > Components: WildFly modules > Affects Versions: 10.0.0.Alpha3, 9.4.6.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 9.4.7.Final, 10.0.0.Beta1 > > > Currently our feature-packs depend on both "sun.jdk" and "jdk.unsupported" in an inconsistent manner. For the latest versions of Wildfly, we need to use the latter, whilst for older ones we need to use the former. Therefore, for all modules that require access to unsupported classes, we must provide an optional dependency on both of the above modules. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9964) Logging incompatibility when deploying modules on older versions of WildFly

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9964?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9964: ---------------------------------- Sprint: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33 (was: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32) > Logging incompatibility when deploying modules on older versions of WildFly > --------------------------------------------------------------------------- > > Key: ISPN-9964 > URL: https://issues.jboss.org/browse/ISPN-9964 > Project: Infinispan > Issue Type: Bug > Components: WildFly modules > Affects Versions: 9.4.6.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 9.4.7.Final > > > Older versions of Wildfly 7.1.x still utilise jboss-logging 3.1.x, whereas the 9.4.x branch uses 3.3.x. Jboss-logging 3.3.x introduced several new method signatures, which results in a {{NoSuchMethodError}} being thrown when infinispan is embedded on a older wildfly version. -To overcome this, it is necessary to make sure that only the method signatures found in both jboss-logging 3.1.x and 3.3.x are utilised.- Explicitly including the required version of jboss-logging in the wildfly-modules ensures that no discrepancy exists. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9968) JCacheStateAwarenessIT failure due to infinispan-remote dependency

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9968?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9968: ---------------------------------- Sprint: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33 (was: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32) > JCacheStateAwarenessIT failure due to infinispan-remote dependency > ------------------------------------------------------------------ > > Key: ISPN-9968 > URL: https://issues.jboss.org/browse/ISPN-9968 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 10.0.0.Beta1 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 9.4.7.Final, 10.0.0.Beta1 > > > ISPN-9554 introduced a dependency on {{infinispan-remote}} on the server/integration/testsuite that results in classes not being loaded as expected. We should remove this dependency and find an alternative solution for ISPN-9554. > JCacheStateAwarenessIT failure cause: > {code:java} > Caused by: java.lang.IllegalArgumentException: Logger implementation class org.infinispan.jcache.logging.Log_$logger has no matching constructor > at org.jboss.logging.Logger$1.run(Logger.java:2562) ~[?:?] > at java.security.AccessController.doPrivileged(Native Method) ~[?:?] > at org.jboss.logging.Logger.getMessageLogger(Logger.java:2529) ~[?:?] > at org.jboss.logging.Logger.getMessageLogger(Logger.java:2516) ~[?:?] > at org.infinispan.commons.logging.LogFactory.getLog(LogFactory.java:18) ~[?:?] > at org.infinispan.jcache.AbstractJCachingProvider.<clinit>(AbstractJCachingProvider.java:23) ~[?:?] > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) ~[?:?] > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) ~[?:?] > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) ~[?:?] > at java.lang.reflect.Constructor.newInstance(Constructor.java:423) ~[?:?] > at java.lang.Class.newInstance(Class.java:442) ~[?:?] > at java.util.ServiceLoader$LazyIterator.nextService(ServiceLoader.java:380) ~[?:?] > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9660) Histogram stats

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9660?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9660: ---------------------------------- Sprint: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33 (was: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32) > Histogram stats > --------------- > > Key: ISPN-9660 > URL: https://issues.jboss.org/browse/ISPN-9660 > Project: Infinispan > Issue Type: Feature Request > Components: JMX, reporting and management > Affects Versions: 9.4.0.Final > Reporter: Tristan Tarrant > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.0.0.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7889) BaseDistributionInterceptor.remoteGet may cause concurrency issues

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-7889?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7889: ---------------------------------- Sprint: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Alpha0, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33 (was: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Alpha0, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32) > BaseDistributionInterceptor.remoteGet may cause concurrency issues > ------------------------------------------------------------------ > > Key: ISPN-7889 > URL: https://issues.jboss.org/browse/ISPN-7889 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.1.0.Alpha1 > Reporter: Radim Vansa > Assignee: Dan Berindei > Priority: Major > Fix For: 10.0.0.Alpha3, 9.4.6.Final > > > {{BaseDistributionInterceptor.remoteGet}} or any call that accesses the context in an async future handler that is called multiple times in parallel may lead to concurrent modifications of the context. > These calls are usually handled using {{CompletableFuture.allOf()}} or using a CF with counter, but if one of the calls results in exceptional completion of the composed future, the processing continues (e.g. with a retry). The other parallel operation handlers are not stopped, though. > {{BaseDistributionInterceptor.remoteGet}} shouldn't be called in parallel because it does not even synchronize regular successful invocations. > A problem like this caused failures in {{GetAllCommandStressTest}}, and the issue was addressed for {{GetAllCommand}} in ISPN-7884. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues August 2019