February 2019 - infinispan-issues

[JBoss JIRA] (IPROTO-84) ProtoSchemaBuilder does not detect duplicated enum constant names

by Adrian Nistor (Jira)

[ https://issues.jboss.org/browse/IPROTO-84?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated IPROTO-84: -------------------------------- Status: Open (was: New) > ProtoSchemaBuilder does not detect duplicated enum constant names > ----------------------------------------------------------------- > > Key: IPROTO-84 > URL: https://issues.jboss.org/browse/IPROTO-84 > Project: Infinispan ProtoStream > Issue Type: Bug > Reporter: Adrian Nistor > Priority: Major > > The duplication is eventually detected later by the proto schema parser, but at this moment the broken schema is already registered and its status is ERROR. Would be better to detect this early during the analysis of the annotations. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-84) ProtoSchemaBuilder does not detect duplicated enum constant names

by Adrian Nistor (Jira)

Adrian Nistor created IPROTO-84: ----------------------------------- Summary: ProtoSchemaBuilder does not detect duplicated enum constant names Key: IPROTO-84 URL: https://issues.jboss.org/browse/IPROTO-84 Project: Infinispan ProtoStream Issue Type: Bug Reporter: Adrian Nistor The duplication is eventually detected later by the proto schema parser, but at this moment the broken schema is already registered and its status is ERROR. Would be better to detect this early during the analysis of the annotations. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9921) Warning instead if exception with 0 capacity node and clustered locks

by Katia Aresti (Jira)

[ https://issues.jboss.org/browse/ISPN-9921?page=com.atlassian.jira.plugin.... ] Katia Aresti updated ISPN-9921: ------------------------------- Summary: Warning instead if exception with 0 capacity node and clustered locks (was: Warning instead if exception with 0 capacity node and locks) > Warning instead if exception with 0 capacity node and clustered locks > --------------------------------------------------------------------- > > Key: ISPN-9921 > URL: https://issues.jboss.org/browse/ISPN-9921 > Project: Infinispan > Issue Type: Enhancement > Components: Clustered Locks > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > Fix For: 10.0.0.Beta1 > > > If we don't specify a number of owners for the locks and the node is a zero capacity node, the actual implementation raises an error, which is not the case when replicated caches are created by the user in this scenario. > Log a warning message instead of an exception for this case and eventually the same warning when the user defines replicated caches and the node is configured as a zero-capacity node -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9921) Warning instead if exception with 0 capacity node and locks

by Katia Aresti (Jira)

[ https://issues.jboss.org/browse/ISPN-9921?page=com.atlassian.jira.plugin.... ] Katia Aresti updated ISPN-9921: ------------------------------- Component/s: Clustered Locks > Warning instead if exception with 0 capacity node and locks > ----------------------------------------------------------- > > Key: ISPN-9921 > URL: https://issues.jboss.org/browse/ISPN-9921 > Project: Infinispan > Issue Type: Enhancement > Components: Clustered Locks > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > Fix For: 10.0.0.Beta1 > > > If we don't specify a number of owners for the locks and the node is a zero capacity node, the actual implementation raises an error, which is not the case when replicated caches are created by the user in this scenario. > Log a warning message instead of an exception for this case and eventually the same warning when the user defines replicated caches and the node is configured as a zero-capacity node -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9921) Warning instead if exception with 0 capacity node and locks

by Katia Aresti (Jira)

[ https://issues.jboss.org/browse/ISPN-9921?page=com.atlassian.jira.plugin.... ] Katia Aresti updated ISPN-9921: ------------------------------- Fix Version/s: 10.0.0.Beta1 > Warning instead if exception with 0 capacity node and locks > ----------------------------------------------------------- > > Key: ISPN-9921 > URL: https://issues.jboss.org/browse/ISPN-9921 > Project: Infinispan > Issue Type: Enhancement > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > Fix For: 10.0.0.Beta1 > > > If we don't specify a number of owners for the locks and the node is a zero capacity node, the actual implementation raises an error, which is not the case when replicated caches are created by the user in this scenario. > Log a warning message instead of an exception for this case and eventually the same warning when the user defines replicated caches and the node is configured as a zero-capacity node -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9921) Warning instead if exception with 0 capacity node and locks

by Katia Aresti (Jira)

[ https://issues.jboss.org/browse/ISPN-9921?page=com.atlassian.jira.plugin.... ] Katia Aresti reassigned ISPN-9921: ---------------------------------- Assignee: Katia Aresti > Warning instead if exception with 0 capacity node and locks > ----------------------------------------------------------- > > Key: ISPN-9921 > URL: https://issues.jboss.org/browse/ISPN-9921 > Project: Infinispan > Issue Type: Enhancement > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > Fix For: 10.0.0.Beta1 > > > If we don't specify a number of owners for the locks and the node is a zero capacity node, the actual implementation raises an error, which is not the case when replicated caches are created by the user in this scenario. > Log a warning message instead of an exception for this case and eventually the same warning when the user defines replicated caches and the node is configured as a zero-capacity node -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9921) Warning instead if exception with 0 capacity node and locks

by Katia Aresti (Jira)

Katia Aresti created ISPN-9921: ---------------------------------- Summary: Warning instead if exception with 0 capacity node and locks Key: ISPN-9921 URL: https://issues.jboss.org/browse/ISPN-9921 Project: Infinispan Issue Type: Enhancement Reporter: Katia Aresti If we don't specify a number of owners for the locks and the node is a zero capacity node, the actual implementation raises an error, which is not the case when replicated caches are created by the user in this scenario. Log a warning message instead of an exception for this case and eventually the same warning when the user defines replicated caches and the node is configured as a zero-capacity node -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9920) Update Netty to 4.1.33.Final

by William Burns (Jira)

William Burns created ISPN-9920: ----------------------------------- Summary: Update Netty to 4.1.33.Final Key: ISPN-9920 URL: https://issues.jboss.org/browse/ISPN-9920 Project: Infinispan Issue Type: Component Upgrade Components: Hot Rod, Server Reporter: William Burns Fix For: 10.0.0.Beta1 Netty is a bit outdated, we should update. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9677) Non-transactional queries don't update the query cache

by Galder Zamarreño (Jira)

[ https://issues.jboss.org/browse/ISPN-9677?page=com.atlassian.jira.plugin.... ] Galder Zamarreño resolved ISPN-9677. ------------------------------------ Resolution: Done > Non-transactional queries don't update the query cache > ------------------------------------------------------ > > Key: ISPN-9677 > URL: https://issues.jboss.org/browse/ISPN-9677 > Project: Infinispan > Issue Type: Bug > Components: Hibernate Cache > Affects Versions: 9.4.1.Final > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Priority: Major > Fix For: 9.4.3.Final, 10.0.0.Alpha1 > > > This is affecting the Hibernate second-level cache simple tutorials where queries are executed outside transactions. > The problem is that the new integration for the query results (result of ISPN-9075) does not verify if there's an on-going transaction before registering a transaction completed synchronization where the query cache is updated. > As a result, when a non-transactional query happens, the transaction synchronization callback does not happen and the query cache is not updated. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9677) Non-transactional queries don't update the query cache

by Galder Zamarreño (Jira)

[ https://issues.jboss.org/browse/ISPN-9677?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-9677: ----------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.7.Final) > Non-transactional queries don't update the query cache > ------------------------------------------------------ > > Key: ISPN-9677 > URL: https://issues.jboss.org/browse/ISPN-9677 > Project: Infinispan > Issue Type: Bug > Components: Hibernate Cache > Affects Versions: 9.4.1.Final > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Priority: Major > Fix For: 10.0.0.Alpha1, 9.4.3.Final > > > This is affecting the Hibernate second-level cache simple tutorials where queries are executed outside transactions. > The problem is that the new integration for the query results (result of ISPN-9075) does not verify if there's an on-going transaction before registering a transaction completed synchronization where the query cache is updated. > As a result, when a non-transactional query happens, the transaction synchronization callback does not happen and the query cache is not updated. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2019