March 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-7650) Refactor tests to testng assertions

by Katia Aresti (JIRA)

[ https://issues.jboss.org/browse/ISPN-7650?page=com.atlassian.jira.plugin.... ] Katia Aresti updated ISPN-7650: ------------------------------- Status: Open (was: New) > Refactor tests to testng assertions > ----------------------------------- > > Key: ISPN-7650 > URL: https://issues.jboss.org/browse/ISPN-7650 > Project: Infinispan > Issue Type: Task > Components: Core > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Trivial > Labels: core-team > Fix For: 9.0.0.CR3 > > > Use testng assertions instead of assert in DistSyncFuncTest and APINonTxTest -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7650) Refactor tests to testng assertions

by Katia Aresti (JIRA)

Katia Aresti created ISPN-7650: ---------------------------------- Summary: Refactor tests to testng assertions Key: ISPN-7650 URL: https://issues.jboss.org/browse/ISPN-7650 Project: Infinispan Issue Type: Task Components: Core Reporter: Katia Aresti Assignee: Katia Aresti Priority: Trivial Fix For: 9.0.0.CR3 Use testng assertions instead of assert in DistSyncFuncTest and APINonTxTest -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6976) Log#iterationClosed should not use INFO level logging

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6976?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-6976: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Log#iterationClosed should not use INFO level logging > ----------------------------------------------------- > > Key: ISPN-6976 > URL: https://issues.jboss.org/browse/ISPN-6976 > Project: Infinispan > Issue Type: Enhancement > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Priority: Minor > Fix For: 9.0.0.Final > > > I'm seeing lots of: > INFO RemoteCloseableIterator:69 - ISPN004046: Successfully closed remote iterator 'ae8525ce-a1f2-4dd8-b365-cce77af47656' > This is better suited for DEBUG level as it refers to normal operations. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7628) Administration console - the cluster status doesn't reflect "reload-required" state of its nodes

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7628?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-7628: ------------------------------- Status: Open (was: New) > Administration console - the cluster status doesn't reflect "reload-required" state of its nodes > ------------------------------------------------------------------------------------------------ > > Key: ISPN-7628 > URL: https://issues.jboss.org/browse/ISPN-7628 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.CR2 > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > > The cluster has "Started" status even though all of its nodes have "reload-required" status. > Expected result: > The cluster status should also be "reload-required" > Another suggestion: > "Reload" action should be available from the cluster so that the user doesn't need to perform this action on individual nodes (there could be hundreds of them ) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7628) Administration console - the cluster status doesn't reflect "reload-required" state of its nodes

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7628?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-7628: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan-management-console/pull/199 > Administration console - the cluster status doesn't reflect "reload-required" state of its nodes > ------------------------------------------------------------------------------------------------ > > Key: ISPN-7628 > URL: https://issues.jboss.org/browse/ISPN-7628 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.CR2 > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > > The cluster has "Started" status even though all of its nodes have "reload-required" status. > Expected result: > The cluster status should also be "reload-required" > Another suggestion: > "Reload" action should be available from the cluster so that the user doesn't need to perform this action on individual nodes (there could be hundreds of them ) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6976) Log#iterationClosed should not use INFO level logging

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-6976?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-6976: ---------------------------------- Status: Open (was: New) > Log#iterationClosed should not use INFO level logging > ----------------------------------------------------- > > Key: ISPN-6976 > URL: https://issues.jboss.org/browse/ISPN-6976 > Project: Infinispan > Issue Type: Enhancement > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Priority: Minor > Fix For: 9.0.0.Final > > > I'm seeing lots of: > INFO RemoteCloseableIterator:69 - ISPN004046: Successfully closed remote iterator 'ae8525ce-a1f2-4dd8-b365-cce77af47656' > This is better suited for DEBUG level as it refers to normal operations. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6976) Log#iterationClosed should not use INFO level logging

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-6976?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-6976: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5002 > Log#iterationClosed should not use INFO level logging > ----------------------------------------------------- > > Key: ISPN-6976 > URL: https://issues.jboss.org/browse/ISPN-6976 > Project: Infinispan > Issue Type: Enhancement > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Priority: Minor > Fix For: 9.0.0.Final > > > I'm seeing lots of: > INFO RemoteCloseableIterator:69 - ISPN004046: Successfully closed remote iterator 'ae8525ce-a1f2-4dd8-b365-cce77af47656' > This is better suited for DEBUG level as it refers to normal operations. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6976) Log#iterationClosed should not use INFO level logging

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-6976?page=com.atlassian.jira.plugin.... ] Sanne Grinovero reassigned ISPN-6976: ------------------------------------- Assignee: Sanne Grinovero > Log#iterationClosed should not use INFO level logging > ----------------------------------------------------- > > Key: ISPN-6976 > URL: https://issues.jboss.org/browse/ISPN-6976 > Project: Infinispan > Issue Type: Enhancement > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Priority: Minor > Fix For: 9.0.0.Final > > > I'm seeing lots of: > INFO RemoteCloseableIterator:69 - ISPN004046: Successfully closed remote iterator 'ae8525ce-a1f2-4dd8-b365-cce77af47656' > This is better suited for DEBUG level as it refers to normal operations. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6029) DDL for JDBC store tables should never allow null

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-6029?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-6029: ------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/4957, https://github.com/infinispan/infinispan/pull/5001 (was: https://github.com/infinispan/infinispan/pull/4957) > DDL for JDBC store tables should never allow null > ------------------------------------------------- > > Key: ISPN-6029 > URL: https://issues.jboss.org/browse/ISPN-6029 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 8.1.0.Final, 8.2.0.Final, 8.0.2.Final, 9.0.0.CR2 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 9.0.0.CR4 > > > The DDL for jdbc persistent stores creates a 3 column table, where only the primary key is not null. However, both the string-based and binary-based cache stores require non-null values for the data column and timestamp column. These columns should not allow null values. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6029) DDL for JDBC store tables should never allow null

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-6029?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-6029: ------------------------------- Fix Version/s: 9.0.0.CR4 > DDL for JDBC store tables should never allow null > ------------------------------------------------- > > Key: ISPN-6029 > URL: https://issues.jboss.org/browse/ISPN-6029 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 8.1.0.Final, 8.2.0.Final, 8.0.2.Final, 9.0.0.CR2 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 9.0.0.CR4 > > > The DDL for jdbc persistent stores creates a 3 column table, where only the primary key is not null. However, both the string-based and binary-based cache stores require non-null values for the data column and timestamp column. These columns should not allow null values. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2017