July 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (IPROTO-105) Accept annotated 'getters' that are not named according to the javabeans standard

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/IPROTO-105?page=com.atlassian.jira.plugin... ] Nistor Adrian updated IPROTO-105: --------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/protostream/pull/72 > Accept annotated 'getters' that are not named according to the javabeans standard > --------------------------------------------------------------------------------- > > Key: IPROTO-105 > URL: https://issues.jboss.org/browse/IPROTO-105 > Project: Infinispan ProtoStream > Issue Type: Enhancement > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 4.3.0.Alpha9, 4.3.0.Final > > > While 'getLifespan()' is and accepted getter for 'lifespan', 'lifespan()' is not, but it would be very useful to add support for this case. > See infinispan's EmbeddedLifespanExpirableMetadata -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-99) Ability to define an empty proto message via Pojo annotations

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/IPROTO-99?page=com.atlassian.jira.plugin.... ] Nistor Adrian updated IPROTO-99: -------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 4.3.0.Final Resolution: Done Merged in master (4.3.x) > Ability to define an empty proto message via Pojo annotations > ------------------------------------------------------------- > > Key: IPROTO-99 > URL: https://issues.jboss.org/browse/IPROTO-99 > Project: Infinispan ProtoStream > Issue Type: Feature Request > Affects Versions: 4.3.0.Alpha7 > Reporter: Ryan Emerson > Assignee: Nistor Adrian > Priority: Major > Fix For: 4.3.0.Alpha9, 4.3.0.Final > > > In some cases it's useful for a empty protobuf message to be sent, for example formalising an implementation type. > Currently when trying to define an empty proto message by annotating a class with just {{ProtoName}} annotation, the following error is thrown at compile time: > {code:java} > Error:(71, 8) java: Class org.infinispan.notifications.cachelistener.cluster.AbstractClusterListenerUtilTest.StringAppender does not have any @ProtoField annotated fields. The class should be either annotated or it should have a custom marshaller. > {code} > It's possible to workaround this by simply creating a {{@Protofield}} annotation on a class variable which is never initialised. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10430) Fix JdbcStringBasedStoreFunctionalTest thread leak

by Katia Aresti (Jira)

Katia Aresti created ISPN-10430: ----------------------------------- Summary: Fix JdbcStringBasedStoreFunctionalTest thread leak Key: ISPN-10430 URL: https://issues.jboss.org/browse/ISPN-10430 Project: Infinispan Issue Type: Bug Reporter: Katia Aresti java.lang.RuntimeException: Leaked threads: {Agroal_756431211: reported, possible sources [org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStoreFunctionalTest, org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStoreVamTest, org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStoreTest, org.infinispan.persistence.jdbc.stringbased.StringStoreWithManagedConnectionTest, org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStoreAltTwoWayMapperTest, org.infinispan.persistence.jdbc.stringbased.StringStoreWithPooledConnectionFunctionalTest, org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStoreAltMapperTest, org.infinispan.persistence.jdbc.stringbased.NonStringKeyPreloadTest, org.infinispan.persistence.jdbc.stringbased.StringStoreWithManagedConnectionFunctionalTest, org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStoreVamAltMapperTest]}, {Agroal_18676467981: reported, possible sources [org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStoreFunctionalTest, org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStoreTest, org.infinispan.persistence.jdbc.stringbased.StringStoreWithManagedConnectionTest, org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStoreAltTwoWayMapperTest, org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedSegmentedStoreTest, org.infinispan.persistence.jdbc.stringbased.StringStoreWithPooledConnectionFunctionalTest, org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStoreAltMapperTest, org.infinispan.persistence.jdbc.stringbased.NonStringKeyPreloadTest]} at org.infinispan.commons.test.ThreadLeakChecker.performCheck(ThreadLeakChecker.java:200) at org.infinispan.commons.test.ThreadLeakChecker.checkForLeaks(ThreadLeakChecker.java:165) at org.infinispan.commons.test.TestNGSuiteChecksTest.afterSuite(TestNGSuiteChecksTest.java:46) ... Removed 25 stack frames -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9929) Remote configuration API

by Katia Aresti (Jira)

[ https://issues.jboss.org/browse/ISPN-9929?page=com.atlassian.jira.plugin.... ] Katia Aresti updated ISPN-9929: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7167 > Remote configuration API > ------------------------ > > Key: ISPN-9929 > URL: https://issues.jboss.org/browse/ISPN-9929 > Project: Infinispan > Issue Type: Sub-task > Components: API > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > > Make the actual configuration of clients work with the reactive cache API. > Make an administration equivalent API -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9929) Remote configuration API

by Katia Aresti (Jira)

[ https://issues.jboss.org/browse/ISPN-9929?page=com.atlassian.jira.plugin.... ] Katia Aresti updated ISPN-9929: ------------------------------- Description: Make the actual configuration of clients work with the reactive cache API. Make an administration equivalent API was:Make the actual configuration of clients work with the reactive cache API > Remote configuration API > ------------------------ > > Key: ISPN-9929 > URL: https://issues.jboss.org/browse/ISPN-9929 > Project: Infinispan > Issue Type: Sub-task > Components: API > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > > Make the actual configuration of clients work with the reactive cache API. > Make an administration equivalent API -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10429) Hot Rod client doesn't retry on socket timeout

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10429?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10429: ----------------------------------- Status: Open (was: New) > Hot Rod client doesn't retry on socket timeout > ---------------------------------------------- > > Key: ISPN-10429 > URL: https://issues.jboss.org/browse/ISPN-10429 > Project: Infinispan > Issue Type: Bug > Components: Hot Rod > Affects Versions: 10.0.0.Beta4, 9.4.15.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.Beta5 > > > The Hot Rod client registers a timeout handler for operations using the socket timeout. However when this timeout is hit, the retry logic is not invoked causing requests to dead servers to fail immediately without retry. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10429) Hot Rod client doesn't retry on socket timeout

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10429?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10429: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7166 > Hot Rod client doesn't retry on socket timeout > ---------------------------------------------- > > Key: ISPN-10429 > URL: https://issues.jboss.org/browse/ISPN-10429 > Project: Infinispan > Issue Type: Bug > Components: Hot Rod > Affects Versions: 10.0.0.Beta4, 9.4.15.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.Beta5 > > > The Hot Rod client registers a timeout handler for operations using the socket timeout. However when this timeout is hit, the retry logic is not invoked causing requests to dead servers to fail immediately without retry. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10429) Hot Rod client doesn't retry on socket timeout

by Tristan Tarrant (Jira)

Tristan Tarrant created ISPN-10429: -------------------------------------- Summary: Hot Rod client doesn't retry on socket timeout Key: ISPN-10429 URL: https://issues.jboss.org/browse/ISPN-10429 Project: Infinispan Issue Type: Bug Components: Hot Rod Affects Versions: 9.4.15.Final, 10.0.0.Beta4 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 10.0.0.Beta5 The Hot Rod client registers a timeout handler for operations using the socket timeout. However when this timeout is hit, the retry logic is not invoked causing requests to dead servers to fail immediately without retry. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10428) Incorrect XSD description for configuration of file-store

by Wolf-Dieter Fink (Jira)

Wolf-Dieter Fink created ISPN-10428: --------------------------------------- Summary: Incorrect XSD description for configuration of file-store Key: ISPN-10428 URL: https://issues.jboss.org/browse/ISPN-10428 Project: Infinispan Issue Type: Bug Components: Core, Server Environment: XSD jboss-infinispan-core*.xsd infinispan-config*.xsd Reporter: Wolf-Dieter Fink Embedded and server mode are using a different configuration for file-store embedded : infinispan-config* {code} </xs:attribute> <xs:attribute name="relative-to" type="xs:string"> <xs:annotation><xs:documentation>Unused XML attribute</xs:documentation></xs:annotation> </xs:attribute> <xs:attribute name="path" type="xs:string"> <xs:annotation> <xs:documentation> The path within "relative-to" in which to store the cache state. If undefined, the path defaults to the cache container name. </xs:documentation> </xs:annotation> </xs:attribute> </xs:extension> </xs:complexContent> </xs:complexType> {code} Here the relative-to is not used but referenced for path. But path is used relative to PWD if it is not an absolute one, also if defaults to 'Infinispan-SingleFileStore' if not set. For the server configuration it is {code} <xs:attribute name="relative-to" type="xs:string" default="jboss.server.data.dir"> <xs:annotation> <xs:documentation>The base directory in which to store the cache state.</xs:documentation> </xs:annotation> </xs:attribute> <xs:attribute name="path" type="xs:string"> <xs:annotation> <xs:documentation> The path within "relative-to" in which to store the cache state. If undefined, the path defaults to the cache container name. </xs:documentation> </xs:annotation> </xs:attribute> {code} But relative-to is a reference to a path declaration like this {code} <paths> <path name="my.dir" path="/MyCacheStore"/> </paths> ... <distributed-cache name="wolf"> <persistence> <file-store shared="false" fetch-state="true" relative-to="my.dir"/> </persistence> </distributed-cache> {code} If relative-to is set to a real path or env variable the server start will fail with {code} ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.datagrid-infinispan.clustered.wolf.config: org.jboss.msc.service.StartException in service jboss.datagrid-infinispan.clustered.wolf.config: Failed to start service ... Caused by: java.lang.IllegalArgumentException: WFLYCTL0256: Could not find a path called '/MyCacheStore' at org.jboss.as.controller.services.path.PathManagerService.resolveRelativePathEntry(PathManagerService.java:110) at org.jboss.as.clustering.infinispan.subsystem.CacheConfigurationAdd$5.inject(CacheConfigurationAdd.java:765) at org.jboss.as.clustering.infinispan.subsystem.CacheConfigurationAdd$5.inject(CacheConfigurationAdd.java:760) at org.jboss.msc.inject.CastingInjector.inject(CastingInjector.java:58) at org.jboss.msc.service.ServiceControllerImpl.inject(ServiceControllerImpl.java:1517) at org.jboss.msc.service.ServiceControllerImpl.inject(ServiceControllerImpl.java:1503) at org.jboss.msc.service.ServiceControllerImpl.access$2800(ServiceControllerImpl.java:55) at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1699) ... 6 more {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10422) Deprecate MediaType::parse in favour of MediaType::fromString

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/ISPN-10422?page=com.atlassian.jira.plugin... ] Nistor Adrian updated ISPN-10422: --------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Merged in master. > Deprecate MediaType::parse in favour of MediaType::fromString > ------------------------------------------------------------- > > Key: ISPN-10422 > URL: https://issues.jboss.org/browse/ISPN-10422 > Project: Infinispan > Issue Type: Enhancement > Components: API > Affects Versions: 10.0.0.Beta4 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta5 > > > Currently {{org.infinispan.commons.dataconversion.MediaType}} exposes both {{fromString}} and {{parse}} methods to create an instance from a String. We should deprecate the latter in favour of the former and update all internal code references. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues July 2019