February 2016 - infinispan-issues

[JBoss JIRA] (ISPN-6275) Double invalidate of invalid Hot Rod connections

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6275?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-6275: ------------------------------------- Assignee: Galder Zamarreño > Double invalidate of invalid Hot Rod connections > ------------------------------------------------ > > Key: ISPN-6275 > URL: https://issues.jboss.org/browse/ISPN-6275 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 6.0.2.Final > Reporter: Dennis Reed > Assignee: Galder Zamarreño > > When there's a problem with a Hot Rod operation, RetryOnFailureOperation invalidates the connection twice (once in a catch block, and once in a finally block). > This causes the GenericKeyedObjectPool counts to get off, and anything relying on that count (such as the maxTotal configuration for the pool) to break. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6257) Management console - stopping a cluster breaks cluster tab

by Roman Macor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6257?page=com.atlassian.jira.plugin.... ] Roman Macor resolved ISPN-6257. ------------------------------- Resolution: Done Works well with the latest snapshot. > Management console - stopping a cluster breaks cluster tab > ---------------------------------------------------------- > > Key: ISPN-6257 > URL: https://issues.jboss.org/browse/ISPN-6257 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > > Steps to reproduce: > Clusters tab -> click on cluster -> actions -> stop > Click on clusters tab again -> > Links to go to specific clusters (e.g. main-server-group) no longer work. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6257) Management console - stopping a cluster breaks cluster tab

by Roman Macor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6257?page=com.atlassian.jira.plugin.... ] Roman Macor updated ISPN-6257: ------------------------------ Comment: was deleted (was: Works well with the latest snapshot.) > Management console - stopping a cluster breaks cluster tab > ---------------------------------------------------------- > > Key: ISPN-6257 > URL: https://issues.jboss.org/browse/ISPN-6257 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > > Steps to reproduce: > Clusters tab -> click on cluster -> actions -> stop > Click on clusters tab again -> > Links to go to specific clusters (e.g. main-server-group) no longer work. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6257) Management console - stopping a cluster breaks cluster tab

by Roman Macor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6257?page=com.atlassian.jira.plugin.... ] Roman Macor commented on ISPN-6257: ----------------------------------- Works well with the latest snapshot. > Management console - stopping a cluster breaks cluster tab > ---------------------------------------------------------- > > Key: ISPN-6257 > URL: https://issues.jboss.org/browse/ISPN-6257 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > > Steps to reproduce: > Clusters tab -> click on cluster -> actions -> stop > Click on clusters tab again -> > Links to go to specific clusters (e.g. main-server-group) no longer work. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6149) Management console - refresh button on cluster detail page doesn't work properly

by Roman Macor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6149?page=com.atlassian.jira.plugin.... ] Roman Macor commented on ISPN-6149: ----------------------------------- The refresh button changes status properly now. However, pressing refresh twice quickly still displays nodes twice. (see the screenshot) > Management console - refresh button on cluster detail page doesn't work properly > -------------------------------------------------------------------------------- > > Key: ISPN-6149 > URL: https://issues.jboss.org/browse/ISPN-6149 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Attachments: Screenshot-refresh.png > > > Clusters tab -> click on cluster > Actions -> stop -> wait for cluster to stop -> refresh > - cluster status doesn't change (should be "stopped"), after pressing refresh again cluster status disappears > Another issue: > - Pressing refresh repeatably results in nodes being displayed more than once (please see attached screenshot) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6276) Non-threadsafe use of HashSet in AdvancedAsyncCacheLoader

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6276?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec reassigned ISPN-6276: ----------------------------------------- Assignee: Sebastian Łaskawiec > Non-threadsafe use of HashSet in AdvancedAsyncCacheLoader > ---------------------------------------------------------- > > Key: ISPN-6276 > URL: https://issues.jboss.org/browse/ISPN-6276 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 6.0.2.Final > Reporter: Dennis Reed > Assignee: Sebastian Łaskawiec > > org.infinispan.persistence.async.AdvancedAsyncCacheLoader$process creates a HashSet, and passes it to loadAllKeys(). > loadAllKeys() creates a task to get each key and add it to the HashSet. > This task is run by org.infinispan.persistence.file.SingleFileStore#process, which runs it in multiple threads at once (one thread per key). > There is no synchronization on that HashSet that is shared by the multiple threads. > HashSet is not thread safe. One known side effect of non-synchronized access by multiple threads is infinite loops, which has been witnessed here. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6262) Make parallel build passing

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6262?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec commented on ISPN-6262: ------------------------------------------- Yes, this is a broader problem and it seems there is no "quick and easy" solution. > Make parallel build passing > --------------------------- > > Key: ISPN-6262 > URL: https://issues.jboss.org/browse/ISPN-6262 > Project: Infinispan > Issue Type: Bug > Components: Build process > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Priority: Trivial > Fix For: 8.2.0.CR1 > > > At the moment parallel build {{./build.sh clean install -DskipTests -T4}} often fails. It would be nice to fix it and make building much faster. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6276) Non-threadsafe use of HashSet in AdvancedAsyncCacheLoader

by Dennis Reed (JIRA)

Dennis Reed created ISPN-6276: --------------------------------- Summary: Non-threadsafe use of HashSet in AdvancedAsyncCacheLoader Key: ISPN-6276 URL: https://issues.jboss.org/browse/ISPN-6276 Project: Infinispan Issue Type: Bug Components: Loaders and Stores Affects Versions: 6.0.2.Final Reporter: Dennis Reed org.infinispan.persistence.async.AdvancedAsyncCacheLoader$process creates a HashSet, and passes it to loadAllKeys(). loadAllKeys() creates a task to get each key and add it to the HashSet. This task is run by org.infinispan.persistence.file.SingleFileStore#process, which runs it in multiple threads at once (one thread per key). There is no synchronization on that HashSet that is shared by the multiple threads. HashSet is not thread safe. One known side effect of non-synchronized access by multiple threads is infinite loops, which has been witnessed here. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6276) Non-threadsafe use of HashSet in AdvancedAsyncCacheLoader

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-6276?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-6276: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1312186 Bugzilla Update: Perform > Non-threadsafe use of HashSet in AdvancedAsyncCacheLoader > ---------------------------------------------------------- > > Key: ISPN-6276 > URL: https://issues.jboss.org/browse/ISPN-6276 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 6.0.2.Final > Reporter: Dennis Reed > > org.infinispan.persistence.async.AdvancedAsyncCacheLoader$process creates a HashSet, and passes it to loadAllKeys(). > loadAllKeys() creates a task to get each key and add it to the HashSet. > This task is run by org.infinispan.persistence.file.SingleFileStore#process, which runs it in multiple threads at once (one thread per key). > There is no synchronization on that HashSet that is shared by the multiple threads. > HashSet is not thread safe. One known side effect of non-synchronized access by multiple threads is infinite loops, which has been witnessed here. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6275) Double invalidate of invalid Hot Rod connections

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-6275?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-6275: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1312185 Bugzilla Update: Perform > Double invalidate of invalid Hot Rod connections > ------------------------------------------------ > > Key: ISPN-6275 > URL: https://issues.jboss.org/browse/ISPN-6275 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 6.0.2.Final > Reporter: Dennis Reed > > When there's a problem with a Hot Rod operation, RetryOnFailureOperation invalidates the connection twice (once in a catch block, and once in a finally block). > This causes the GenericKeyedObjectPool counts to get off, and anything relying on that count (such as the maxTotal configuration for the pool) to break. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2016