September 2015 - infinispan-issues

[JBoss JIRA] (ISPN-5785) Make the GMS join timeout overridable in the server

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5785?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5785: ------------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3721 > Make the GMS join timeout overridable in the server > --------------------------------------------------- > > Key: ISPN-5785 > URL: https://issues.jboss.org/browse/ISPN-5785 > Project: Infinispan > Issue Type: Enhancement > Components: Server > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 8.1.0.Alpha1 > > > The default JGroups configuration in the server has a join timeout of 15s, causing the server in clustered or domain mode to take >20s to start (in non clustered it takes < 5s). Ideally this timeout should be easily configured via command line so that integration tests and docker images can benefit from it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5785) Make the GMS join timeout overridable in the server

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5785?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes reassigned ISPN-5785: --------------------------------------- Assignee: Gustavo Fernandes > Make the GMS join timeout overridable in the server > --------------------------------------------------- > > Key: ISPN-5785 > URL: https://issues.jboss.org/browse/ISPN-5785 > Project: Infinispan > Issue Type: Enhancement > Components: Server > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 8.1.0.Alpha1 > > > The default JGroups configuration in the server has a join timeout of 15s, causing the server in clustered or domain mode to take >20s to start (in non clustered it takes < 5s). Ideally this timeout should be easily configured via command line so that integration tests and docker images can benefit from it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5785) Make the GMS join timeout overridable in the server

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5785?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5785: ------------------------------------ Fix Version/s: 8.1.0.Alpha1 > Make the GMS join timeout overridable in the server > --------------------------------------------------- > > Key: ISPN-5785 > URL: https://issues.jboss.org/browse/ISPN-5785 > Project: Infinispan > Issue Type: Enhancement > Components: Server > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 8.1.0.Alpha1 > > > The default JGroups configuration in the server has a join timeout of 15s, causing the server in clustered or domain mode to take >20s to start (in non clustered it takes < 5s). Ideally this timeout should be easily configured via command line so that integration tests and docker images can benefit from it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5785) Make the GMS join timeout overridable in the server

by Gustavo Fernandes (JIRA)

Gustavo Fernandes created ISPN-5785: --------------------------------------- Summary: Make the GMS join timeout overridable in the server Key: ISPN-5785 URL: https://issues.jboss.org/browse/ISPN-5785 Project: Infinispan Issue Type: Enhancement Components: Server Reporter: Gustavo Fernandes The default JGroups configuration in the server has a join timeout of 15s, causing the server in clustered or domain mode to take >20s to start (in non clustered it takes < 5s). Ideally this timeout should be easily configured via command line so that integration tests and docker images can benefit from it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2201) Make a distinction between user-level and internal flags

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2201?page=com.atlassian.jira.plugin.... ] Galder Zamarreño resolved ISPN-2201. ------------------------------------ Fix Version/s: 8.0.0.Final Resolution: Done This functionality to separate between user-level and internal flags is possible with the new functional map API > Make a distinction between user-level and internal flags > -------------------------------------------------------- > > Key: ISPN-2201 > URL: https://issues.jboss.org/browse/ISPN-2201 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 8.0.0.Final > > > This confusion is highlighted by ISPN-2187. > User-level flags, i.e. FORCE_WRITE_LOCK, should be separated from those that are purely internal, i.e. PUT_FOR_EXTERNAL_READ. > Obviously, user-level flags might be used for internal purpouses, but by making the separation and putting the internal-only flags separately, we should avoid misuse. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5781) Upgrade server to WildFly 10.0.0.CR1

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5781?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-5781: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 8.1.0.Alpha1 Resolution: Done > Upgrade server to WildFly 10.0.0.CR1 > ------------------------------------ > > Key: ISPN-5781 > URL: https://issues.jboss.org/browse/ISPN-5781 > Project: Infinispan > Issue Type: Task > Components: Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 8.1.0.Alpha1, 8.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5629) AvgAccumulator should handle NaN and other non-numbers

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5629?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-5629: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/3717 > AvgAccumulator should handle NaN and other non-numbers > ------------------------------------------------------ > > Key: ISPN-5629 > URL: https://issues.jboss.org/browse/ISPN-5629 > Project: Infinispan > Issue Type: Bug > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.1.0.Final > > > The handling should be similar to java.util.DoubleSummaryStatistics -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5783) Cache.put(null, null) leaks an implicit transaction

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5783?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5783: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3718 > Cache.put(null, null) leaks an implicit transaction > --------------------------------------------------- > > Key: ISPN-5783 > URL: https://issues.jboss.org/browse/ISPN-5783 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.0.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 8.1.0.Alpha1 > > > {{null}} keys and values are not supported, and {{Cache.put(null, null)}} will throw a {{NullPointerException}}. But the null check happens after the implicit transaction was created, and it doesn't clean it up before throwing the exception. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5784) [CLI] Cant connect to infinispan server via CLI

by Andrea Cosentino (JIRA)

[ https://issues.jboss.org/browse/ISPN-5784?page=com.atlassian.jira.plugin.... ] Andrea Cosentino commented on ISPN-5784: ---------------------------------------- Same problem here. > [CLI] Cant connect to infinispan server via CLI > ----------------------------------------------- > > Key: ISPN-5784 > URL: https://issues.jboss.org/browse/ISPN-5784 > Project: Infinispan > Issue Type: Bug > Components: CLI > Affects Versions: 8.0.0.Final, 8.0.1.Final > Reporter: Vitalii Chepeliuk > Priority: Blocker > > *container* command does not show all available containers > [disconnected /] connect > [standalone@localhost:9990 /] container > [standalone@localhost:9990 /] > [standalone@localhost:9990 /] cd subsystem=datagrid-infinispan/cache-container=local > [standalone@localhost:9990 cache-container=local] > alias connection-info encoding ls roles unset > abort container end module rollback upgrade > batch create evict patch run-batch version > begin data-source get put set xa-data-source > cache deny grant pwd shutdown : > cd deploy help quit site > clear deployment-info history read-attribute start > clearcache deployment-overlay if read-operation stats > command echo info reload try > connect echo-dmr jdbc-driver-info replace undeploy > *cache* command shows no resources registered > [standalone@localhost:9990 cache-container=local] cache default > WFLYCTL0030: No resource definition is registered for address [ > ("subsystem" => "infinispan"), > ("cache-container" => "local") > ] > [standalone@localhost:9990 cache-container=local] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5784) [CLI] Cant connect to infinispan server via CLI

by Vitalii Chepeliuk (JIRA)

[ https://issues.jboss.org/browse/ISPN-5784?page=com.atlassian.jira.plugin.... ] Vitalii Chepeliuk updated ISPN-5784: ------------------------------------ Priority: Blocker (was: Critical) > [CLI] Cant connect to infinispan server via CLI > ----------------------------------------------- > > Key: ISPN-5784 > URL: https://issues.jboss.org/browse/ISPN-5784 > Project: Infinispan > Issue Type: Bug > Components: CLI > Affects Versions: 8.0.0.Final, 8.0.1.Final > Reporter: Vitalii Chepeliuk > Priority: Blocker > > *container* command does not show all available containers > [disconnected /] connect > [standalone@localhost:9990 /] container > [standalone@localhost:9990 /] > [standalone@localhost:9990 /] cd subsystem=datagrid-infinispan/cache-container=local > [standalone@localhost:9990 cache-container=local] > alias connection-info encoding ls roles unset > abort container end module rollback upgrade > batch create evict patch run-batch version > begin data-source get put set xa-data-source > cache deny grant pwd shutdown : > cd deploy help quit site > clear deployment-info history read-attribute start > clearcache deployment-overlay if read-operation stats > command echo info reload try > connect echo-dmr jdbc-driver-info replace undeploy > *cache* command shows no resources registered > [standalone@localhost:9990 cache-container=local] cache default > WFLYCTL0030: No resource definition is registered for address [ > ("subsystem" => "infinispan"), > ("cache-container" => "local") > ] > [standalone@localhost:9990 cache-container=local] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues September 2015