October 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-10694) Upgrade to protostream 4.3.0.Alpha13

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/ISPN-10694?page=com.atlassian.jira.plugin... ] Nistor Adrian updated ISPN-10694: --------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Upgrade to protostream 4.3.0.Alpha13 > ------------------------------------ > > Key: ISPN-10694 > URL: https://issues.jboss.org/browse/ISPN-10694 > Project: Infinispan > Issue Type: Component Upgrade > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.0.0.CR3 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10618) If Expiration is enabled the cretionDate is modified to the current server start date if preload is enabled for a persistence

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10618?page=com.atlassian.jira.plugin... ] Will Burns updated ISPN-10618: ------------------------------ Status: Pull Request Sent (was: Reopened) Git Pull Request: https://github.com/infinispan/infinispan/pull/7348, https://github.com/infinispan/infinispan/pull/7347 > If Expiration is enabled the cretionDate is modified to the current server start date if preload is enabled for a persistence > ----------------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-10618 > URL: https://issues.jboss.org/browse/ISPN-10618 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 10.0.0.CR2 > Environment: Cache configuration with preload > <local-cache name="default"> > <persistence> > <file-store shared="false" preload="true" fetch-state="true"/> > </persistence> > </local-cache> > Reporter: Wolf-Dieter Fink > Assignee: Will Burns > Priority: Blocker > Fix For: 10.0.0.CR3, 9.4.17.Final > > > If a cache store entries with expiration the MetaData creationTime is used to calculate the expiration. > This works correct if the server is not restarted or preload=false for the store. > If preload is enabled and the server preload the date the creationTime is set to the current server start time. > In this case all expiration for existing entries is not working correctly -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10618) If Expiration is enabled the cretionDate is modified to the current server start date if preload is enabled for a persistence

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10618?page=com.atlassian.jira.plugin... ] Will Burns updated ISPN-10618: ------------------------------ Fix Version/s: 10.0.0.CR3 9.4.17.Final > If Expiration is enabled the cretionDate is modified to the current server start date if preload is enabled for a persistence > ----------------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-10618 > URL: https://issues.jboss.org/browse/ISPN-10618 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 10.0.0.CR2 > Environment: Cache configuration with preload > <local-cache name="default"> > <persistence> > <file-store shared="false" preload="true" fetch-state="true"/> > </persistence> > </local-cache> > Reporter: Wolf-Dieter Fink > Assignee: Will Burns > Priority: Blocker > Fix For: 10.0.0.CR3, 9.4.17.Final > > > If a cache store entries with expiration the MetaData creationTime is used to calculate the expiration. > This works correct if the server is not restarted or preload=false for the store. > If preload is enabled and the server preload the date the creationTime is set to the current server start time. > In this case all expiration for existing entries is not working correctly -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10618) If Expiration is enabled the cretionDate is modified to the current server start date if preload is enabled for a persistence

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10618?page=com.atlassian.jira.plugin... ] Will Burns reopened ISPN-10618: ------------------------------- > If Expiration is enabled the cretionDate is modified to the current server start date if preload is enabled for a persistence > ----------------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-10618 > URL: https://issues.jboss.org/browse/ISPN-10618 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 10.0.0.CR2 > Environment: Cache configuration with preload > <local-cache name="default"> > <persistence> > <file-store shared="false" preload="true" fetch-state="true"/> > </persistence> > </local-cache> > Reporter: Wolf-Dieter Fink > Assignee: Will Burns > Priority: Blocker > Fix For: 10.0.0.CR3, 9.4.17.Final > > > If a cache store entries with expiration the MetaData creationTime is used to calculate the expiration. > This works correct if the server is not restarted or preload=false for the store. > If preload is enabled and the server preload the date the creationTime is set to the current server start time. > In this case all expiration for existing entries is not working correctly -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10640) Expiration creation/lastUsed timestamp are lost when preloading from store

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10640?page=com.atlassian.jira.plugin... ] Will Burns closed ISPN-10640. ----------------------------- Resolution: Duplicate Issue Duplicate of ISPN-10618 > Expiration creation/lastUsed timestamp are lost when preloading from store > -------------------------------------------------------------------------- > > Key: ISPN-10640 > URL: https://issues.jboss.org/browse/ISPN-10640 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 9.4.16.Final > Environment: Cache configuration with preload > <local-cache name="default"> > <persistence> > <file-store shared="false" preload="true" fetch-state="true"/> > </persistence> > </local-cache> > Reporter: Will Burns > Assignee: Will Burns > Priority: Critical > Fix For: 10.0.0.CR3, 9.4.17.Final > > > If a cache store entries with expiration the MetaData creationTime is used to calculate the expiration. > This works correct if the server is not restarted or preload=false for the store. > If preload is enabled and the server preload the date the creationTime is set to the current server start time. > In this case all expiration for existing entries is not working correctly -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10618) If Expiration is enabled the cretionDate is modified to the current server start date if preload is enabled for a persistence

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10618?page=com.atlassian.jira.plugin... ] Will Burns commented on ISPN-10618: ----------------------------------- Actually I can close the other as a duplicate I guess :) > If Expiration is enabled the cretionDate is modified to the current server start date if preload is enabled for a persistence > ----------------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-10618 > URL: https://issues.jboss.org/browse/ISPN-10618 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 10.0.0.CR2 > Environment: Cache configuration with preload > <local-cache name="default"> > <persistence> > <file-store shared="false" preload="true" fetch-state="true"/> > </persistence> > </local-cache> > Reporter: Wolf-Dieter Fink > Assignee: Will Burns > Priority: Blocker > > If a cache store entries with expiration the MetaData creationTime is used to calculate the expiration. > This works correct if the server is not restarted or preload=false for the store. > If preload is enabled and the server preload the date the creationTime is set to the current server start time. > In this case all expiration for existing entries is not working correctly -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10618) If Expiration is enabled the cretionDate is modified to the current server start date if preload is enabled for a persistence

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10618?page=com.atlassian.jira.plugin... ] Will Burns resolved ISPN-10618. ------------------------------- Resolution: Duplicate Issue This is a duplicate of ISPN-10640 > If Expiration is enabled the cretionDate is modified to the current server start date if preload is enabled for a persistence > ----------------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-10618 > URL: https://issues.jboss.org/browse/ISPN-10618 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 10.0.0.CR2 > Environment: Cache configuration with preload > <local-cache name="default"> > <persistence> > <file-store shared="false" preload="true" fetch-state="true"/> > </persistence> > </local-cache> > Reporter: Wolf-Dieter Fink > Assignee: Will Burns > Priority: Blocker > > If a cache store entries with expiration the MetaData creationTime is used to calculate the expiration. > This works correct if the server is not restarted or preload=false for the store. > If preload is enabled and the server preload the date the creationTime is set to the current server start time. > In this case all expiration for existing entries is not working correctly -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10710) Document migrating start the server guide from 9.4 to 10.0

by Diego Lovison (Jira)

[ https://issues.jboss.org/browse/ISPN-10710?page=com.atlassian.jira.plugin... ] Diego Lovison edited comment on ISPN-10710 at 10/2/19 12:45 PM: ---------------------------------------------------------------- Tristan is taking a look for {{"double" property resolution for the bind address}} https://github.com/infinispan/infinispan/pull/7389/files was (Author: dlovison): Tristan is taking a look for {{"double" property resolution for the bind address}} > Document migrating start the server guide from 9.4 to 10.0 > ---------------------------------------------------------- > > Key: ISPN-10710 > URL: https://issues.jboss.org/browse/ISPN-10710 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Servers > Reporter: Diego Lovison > Assignee: Donald Naro > Priority: Critical > Fix For: 10.0.0.CR2 > > > *Migrating start the server guide from 9.4 to 10.0* > * {{./standalone.sh -c clustered.xml}} now is {{./server.sh -j udp}} The server is clustered and is using TCP by default > * {{./standalone.sh}} now is {{./server.sh -c infinispan-local.xml}} > * {{-Djboss.default.multicast.address=234.99.54.20}} should be {{-Djgroups.mcast_addr=234.99.54.20}} > * If you need custom address for UDP or TCP use -{{Djgroups.udp.address=172.18.1.13}} OR {{-Djgroups.tcp.address=172.18.1.13}} > * {{-Djboss.bind.address=172.18.1.13}} should be {{-Djgroups.bind.address=172.18.1.13}} > * {{-Djboss.default.jgroups.stack=udp}} now is {{-j udp}} > * {{-b 0.0.0.0}} now is {{-Dinfinispan.bind.address=GLOBAL}} > * -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10710) Document migrating start the server guide from 9.4 to 10.0

by Diego Lovison (Jira)

[ https://issues.jboss.org/browse/ISPN-10710?page=com.atlassian.jira.plugin... ] Diego Lovison updated ISPN-10710: --------------------------------- Description: *Migrating start the server guide from 9.4 to 10.0* * {{./standalone.sh -c clustered.xml}} now is {{./server.sh -j udp}} The server is clustered and is using TCP by default * {{./standalone.sh}} now is {{./server.sh -c infinispan-local.xml}} * {{-Djboss.default.multicast.address=234.99.54.20}} should be {{-Djgroups.mcast_addr=234.99.54.20}} * If you need custom address for UDP or TCP use -{{Djgroups.udp.address=172.18.1.13}} OR {{-Djgroups.tcp.address=172.18.1.13}} * {{-Djboss.bind.address=172.18.1.13}} should be {{-Djgroups.bind.address=172.18.1.13}} * {{-Djboss.default.jgroups.stack=udp}} now is {{-j udp}} * {{-b 0.0.0.0}} now is {{-Dinfinispan.bind.address=GLOBAL}} * was: *Migrating start the server guide from 9.4 to 10.0* * {{./standalone.sh -c clustered.xml}} now is {{./server.sh -j udp}} The server is clustered and is using TCP by default * {{./standalone.sh}} now is {{./server.sh -c infinispan-local.xml}} * {{-Djboss.default.multicast.address=234.99.54.20}} should be {{-Djgroups.mcast_addr=234.99.54.20}} * {{-Djboss.bind.address=172.18.1.13}} should be -{{Djgroups.udp.address=172.18.1.13}} when working with a UDP transport * {{-Djboss.bind.address=172.18.1.13}} should be {{-Djgroups.tcp.address=172.18.1.13}} when working with a TCP transport * {{-Djboss.default.jgroups.stack=udp}} now is {{-j udp}} * {{-b 0.0.0.0}} now is {{-Dinfinispan.bind.address=GLOBAL}} > Document migrating start the server guide from 9.4 to 10.0 > ---------------------------------------------------------- > > Key: ISPN-10710 > URL: https://issues.jboss.org/browse/ISPN-10710 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Servers > Reporter: Diego Lovison > Assignee: Donald Naro > Priority: Critical > Fix For: 10.0.0.CR2 > > > *Migrating start the server guide from 9.4 to 10.0* > * {{./standalone.sh -c clustered.xml}} now is {{./server.sh -j udp}} The server is clustered and is using TCP by default > * {{./standalone.sh}} now is {{./server.sh -c infinispan-local.xml}} > * {{-Djboss.default.multicast.address=234.99.54.20}} should be {{-Djgroups.mcast_addr=234.99.54.20}} > * If you need custom address for UDP or TCP use -{{Djgroups.udp.address=172.18.1.13}} OR {{-Djgroups.tcp.address=172.18.1.13}} > * {{-Djboss.bind.address=172.18.1.13}} should be {{-Djgroups.bind.address=172.18.1.13}} > * {{-Djboss.default.jgroups.stack=udp}} now is {{-j udp}} > * {{-b 0.0.0.0}} now is {{-Dinfinispan.bind.address=GLOBAL}} > * -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10711) Use common property for setting jgroups bind address/port

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10711?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10711: ----------------------------------- Status: Open (was: New) > Use common property for setting jgroups bind address/port > --------------------------------------------------------- > > Key: ISPN-10711 > URL: https://issues.jboss.org/browse/ISPN-10711 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration > Affects Versions: 10.0.0.CR2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.CR3 > > > Currently the different JGroups transports in the default configs have specific properties for binding address/port, e.g. jgroups.tcp.address vs jgroups.udp.address. We should have additional properties jgroups.bind.address and jgroups.bind.port which can be applied to all types. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues October 2019