May 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5322) Support replicated cache for PH in a read-only mode

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5322?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5322: ----------------------------------------------- Adrian Nistor <anistor(a)redhat.com> changed the Status of [bug 1223226|https://bugzilla.redhat.com/show_bug.cgi?id=1223226] from POST to MODIFIED > Support replicated cache for PH in a read-only mode > --------------------------------------------------- > > Key: ISPN-5322 > URL: https://issues.jboss.org/browse/ISPN-5322 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Reporter: Wolf-Dieter Fink > Labels: partition_handling > Fix For: 7.2.2.Final, 8.0.0.Alpha1 > > > Current a REPL cache can not enable partition handling. > There is a WARN message that the PH is ignored for replicated mode. > The reason is that if one node leave the cache can become inconsistent. > But for some reason it might be worth to have the cache available as read-only, so there is no way to make the cache inconsistent. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5322) Support replicated cache for PH in a read-only mode

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5322?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5322: ----------------------------------------------- Dan Berindei <dberinde(a)redhat.com> changed the Status of [bug 1223226|https://bugzilla.redhat.com/show_bug.cgi?id=1223226] from ASSIGNED to POST > Support replicated cache for PH in a read-only mode > --------------------------------------------------- > > Key: ISPN-5322 > URL: https://issues.jboss.org/browse/ISPN-5322 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Reporter: Wolf-Dieter Fink > Labels: partition_handling > Fix For: 7.2.2.Final, 8.0.0.Alpha1 > > > Current a REPL cache can not enable partition handling. > There is a WARN message that the PH is ignored for replicated mode. > The reason is that if one node leave the cache can become inconsistent. > But for some reason it might be worth to have the cache available as read-only, so there is no way to make the cache inconsistent. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5322) Support replicated cache for PH in a read-only mode

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5322?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5322: ----------------------------------------------- Dan Berindei <dberinde(a)redhat.com> changed the Status of [bug 1223226|https://bugzilla.redhat.com/show_bug.cgi?id=1223226] from NEW to ASSIGNED > Support replicated cache for PH in a read-only mode > --------------------------------------------------- > > Key: ISPN-5322 > URL: https://issues.jboss.org/browse/ISPN-5322 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Reporter: Wolf-Dieter Fink > Labels: partition_handling > Fix For: 7.2.2.Final, 8.0.0.Alpha1 > > > Current a REPL cache can not enable partition handling. > There is a WARN message that the PH is ignored for replicated mode. > The reason is that if one node leave the cache can become inconsistent. > But for some reason it might be worth to have the cache available as read-only, so there is no way to make the cache inconsistent. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5322) Support replicated cache for PH in a read-only mode

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5322?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-5322: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1223226 > Support replicated cache for PH in a read-only mode > --------------------------------------------------- > > Key: ISPN-5322 > URL: https://issues.jboss.org/browse/ISPN-5322 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Reporter: Wolf-Dieter Fink > Labels: partition_handling > Fix For: 7.2.2.Final, 8.0.0.Alpha1 > > > Current a REPL cache can not enable partition handling. > There is a WARN message that the PH is ignored for replicated mode. > The reason is that if one node leave the cache can become inconsistent. > But for some reason it might be worth to have the cache available as read-only, so there is no way to make the cache inconsistent. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-201) make JDBC cache store use DB transactions for commit/rollback

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-201?page=com.atlassian.jira.plugin.s... ] Tristan Tarrant reassigned ISPN-201: ------------------------------------ Assignee: William Burns > make JDBC cache store use DB transactions for commit/rollback > ------------------------------------------------------------- > > Key: ISPN-201 > URL: https://issues.jboss.org/browse/ISPN-201 > Project: Infinispan > Issue Type: Feature Request > Components: Loaders and Stores > Reporter: Mircea Markus > Assignee: William Burns > Labels: modshape > Fix For: 9.0.0.Final > > > current impl of JDBC cache store does not use DB transaction (nor local transactions/Connection.setAutocommit(false)) for storing the modifications created within a transaction. This might leave the store in an inconsistent state one operation fails during commit. This should be changed to either 1. use local transactions or 2. register the driver as an XAResource and rely on the TM to manage the boundaries. I would go for 1, as it would be more consistent with other CStore implementation (different cache store interceptor should be used for managing the 2'nd approach). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-201) make JDBC cache store use DB transactions for commit/rollback

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-201?page=com.atlassian.jira.plugin.s... ] Tristan Tarrant updated ISPN-201: --------------------------------- Fix Version/s: 9.0.0.Final > make JDBC cache store use DB transactions for commit/rollback > ------------------------------------------------------------- > > Key: ISPN-201 > URL: https://issues.jboss.org/browse/ISPN-201 > Project: Infinispan > Issue Type: Feature Request > Components: Loaders and Stores > Reporter: Mircea Markus > Labels: modshape > Fix For: 9.0.0.Final > > > current impl of JDBC cache store does not use DB transaction (nor local transactions/Connection.setAutocommit(false)) for storing the modifications created within a transaction. This might leave the store in an inconsistent state one operation fails during commit. This should be changed to either 1. use local transactions or 2. register the driver as an XAResource and rely on the TM to manage the boundaries. I would go for 1, as it would be more consistent with other CStore implementation (different cache store interceptor should be used for managing the 2'nd approach). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5483) Using multiple FORK channels with JGroupsTransport never acccepts the view, results in NPE

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/ISPN-5483?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated ISPN-5483: --------------------------------- Status: Open (was: New) > Using multiple FORK channels with JGroupsTransport never acccepts the view, results in NPE > ------------------------------------------------------------------------------------------ > > Key: ISPN-5483 > URL: https://issues.jboss.org/browse/ISPN-5483 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.2.1.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 7.2.2.Final, 8.0.0.Alpha1 > > > The problem is org.infinispan.remoting.transport.jgroups.JGroupsTransport#viewAccepted is never called, because org.infinispan.remoting.transport.jgroups.JGroupsTransport#startJGroupsChannelIfNeeded doesn't call viewAccepted if the connectChannel was requested. But multiple FORK channels are only going to be starting this once for the first one and the view will never be accepted. > ----- > Might be hiding another issue? (i.e. why transport didnt get viewAccepted() called) > {noformat} > 14:54:05,490 INFO [org.infinispan.factories.GlobalComponentRegistry] (ServerService Thread Pool -- 61) ISPN000128: Infinispan version: Infinispan 'Hoptimus Prime' 7.2.1.Final > 14:54:05,489 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 59) MSC000001: Failed to start service jboss.infinispan.ejb.dist: org.jboss.msc.service.StartException in service jboss.infinispan.ejb.dist: org.infinispan.manager.EmbeddedCacheManagerStartupException: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.topology.ClusterTopologyManagerImpl.start() on object of type ClusterTopologyManagerImpl > at org.wildfly.clustering.service.AsynchronousServiceBuilder$1.run(AsynchronousServiceBuilder.java:107) [wildfly-clustering-service-10.0.0.Alpha2-SNAPSHOT.jar:10.0.0.Alpha2-SNAPSHOT] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_31] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_31] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_31] > at org.jboss.threads.JBossThread.run(JBossThread.java:320) [jboss-threads-2.2.0.Final.jar:2.2.0.Final] > Caused by: org.infinispan.manager.EmbeddedCacheManagerStartupException: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.topology.ClusterTopologyManagerImpl.start() on object of type ClusterTopologyManagerImpl > at org.infinispan.factories.GlobalComponentRegistry.start(GlobalComponentRegistry.java:248) > at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:588) > at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:554) > at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:424) > at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:438) > at org.jboss.as.clustering.infinispan.DefaultCacheContainer.getCache(DefaultCacheContainer.java:118) > at org.jboss.as.clustering.infinispan.DefaultCacheContainer.getCache(DefaultCacheContainer.java:109) > at org.wildfly.clustering.infinispan.spi.service.CacheBuilder.start(CacheBuilder.java:79) > at org.wildfly.clustering.service.AsynchronousServiceBuilder$1.run(AsynchronousServiceBuilder.java:102) [wildfly-clustering-service-10.0.0.Alpha2-SNAPSHOT.jar:10.0.0.Alpha2-SNAPSHOT] > ... 4 more > Caused by: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.topology.ClusterTopologyManagerImpl.start() on object of type ClusterTopologyManagerImpl > at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:171) > at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:869) > at org.infinispan.factories.AbstractComponentRegistry.invokeStartMethods(AbstractComponentRegistry.java:638) > at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:627) > at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:530) > at org.infinispan.factories.GlobalComponentRegistry.start(GlobalComponentRegistry.java:226) > ... 12 more > Caused by: java.lang.NullPointerException > at org.infinispan.topology.ClusterTopologyManagerImpl.fetchRebalancingStatusFromCoordinator(ClusterTopologyManagerImpl.java:123) > at org.infinispan.topology.ClusterTopologyManagerImpl.start(ClusterTopologyManagerImpl.java:118) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_31] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_31] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_31] > at java.lang.reflect.Method.invoke(Method.java:483) [rt.jar:1.8.0_31] > at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:168) > ... 17 more > {noformat} > Full log here: > https://gist.githubusercontent.com/rhusar/d9f2c68d9b3fa032084b/raw/8dc962... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5483) Using multiple FORK channels with JGroupsTransport never acccepts the view, results in NPE

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/ISPN-5483?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated ISPN-5483: --------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3484 > Using multiple FORK channels with JGroupsTransport never acccepts the view, results in NPE > ------------------------------------------------------------------------------------------ > > Key: ISPN-5483 > URL: https://issues.jboss.org/browse/ISPN-5483 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.2.1.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 7.2.2.Final, 8.0.0.Alpha1 > > > The problem is org.infinispan.remoting.transport.jgroups.JGroupsTransport#viewAccepted is never called, because org.infinispan.remoting.transport.jgroups.JGroupsTransport#startJGroupsChannelIfNeeded doesn't call viewAccepted if the connectChannel was requested. But multiple FORK channels are only going to be starting this once for the first one and the view will never be accepted. > ----- > Might be hiding another issue? (i.e. why transport didnt get viewAccepted() called) > {noformat} > 14:54:05,490 INFO [org.infinispan.factories.GlobalComponentRegistry] (ServerService Thread Pool -- 61) ISPN000128: Infinispan version: Infinispan 'Hoptimus Prime' 7.2.1.Final > 14:54:05,489 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 59) MSC000001: Failed to start service jboss.infinispan.ejb.dist: org.jboss.msc.service.StartException in service jboss.infinispan.ejb.dist: org.infinispan.manager.EmbeddedCacheManagerStartupException: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.topology.ClusterTopologyManagerImpl.start() on object of type ClusterTopologyManagerImpl > at org.wildfly.clustering.service.AsynchronousServiceBuilder$1.run(AsynchronousServiceBuilder.java:107) [wildfly-clustering-service-10.0.0.Alpha2-SNAPSHOT.jar:10.0.0.Alpha2-SNAPSHOT] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_31] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_31] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_31] > at org.jboss.threads.JBossThread.run(JBossThread.java:320) [jboss-threads-2.2.0.Final.jar:2.2.0.Final] > Caused by: org.infinispan.manager.EmbeddedCacheManagerStartupException: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.topology.ClusterTopologyManagerImpl.start() on object of type ClusterTopologyManagerImpl > at org.infinispan.factories.GlobalComponentRegistry.start(GlobalComponentRegistry.java:248) > at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:588) > at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:554) > at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:424) > at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:438) > at org.jboss.as.clustering.infinispan.DefaultCacheContainer.getCache(DefaultCacheContainer.java:118) > at org.jboss.as.clustering.infinispan.DefaultCacheContainer.getCache(DefaultCacheContainer.java:109) > at org.wildfly.clustering.infinispan.spi.service.CacheBuilder.start(CacheBuilder.java:79) > at org.wildfly.clustering.service.AsynchronousServiceBuilder$1.run(AsynchronousServiceBuilder.java:102) [wildfly-clustering-service-10.0.0.Alpha2-SNAPSHOT.jar:10.0.0.Alpha2-SNAPSHOT] > ... 4 more > Caused by: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.topology.ClusterTopologyManagerImpl.start() on object of type ClusterTopologyManagerImpl > at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:171) > at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:869) > at org.infinispan.factories.AbstractComponentRegistry.invokeStartMethods(AbstractComponentRegistry.java:638) > at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:627) > at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:530) > at org.infinispan.factories.GlobalComponentRegistry.start(GlobalComponentRegistry.java:226) > ... 12 more > Caused by: java.lang.NullPointerException > at org.infinispan.topology.ClusterTopologyManagerImpl.fetchRebalancingStatusFromCoordinator(ClusterTopologyManagerImpl.java:123) > at org.infinispan.topology.ClusterTopologyManagerImpl.start(ClusterTopologyManagerImpl.java:118) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_31] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_31] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_31] > at java.lang.reflect.Method.invoke(Method.java:483) [rt.jar:1.8.0_31] > at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:168) > ... 17 more > {noformat} > Full log here: > https://gist.githubusercontent.com/rhusar/d9f2c68d9b3fa032084b/raw/8dc962... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5485) Refactor DataContainer and various Maps to use new Java 8 classes

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5485?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5485: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/3482 > Refactor DataContainer and various Maps to use new Java 8 classes > ----------------------------------------------------------------- > > Key: ISPN-5485 > URL: https://issues.jboss.org/browse/ISPN-5485 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Reporter: William Burns > Assignee: William Burns > Fix For: 8.0.0.Alpha1, 8.0.0.Final > > > Currently we have a lot of stop gap interfaces such as KeyValueAction that have now been replaced by newer Java 8 classes. We should move our classes over to remove redundant code and also provide more consistency. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5486) SemaphoreCompletionService exceptions are never checked

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5486?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5486: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/3482, https://github.com/infinispan/infinispan/pull/3483 > SemaphoreCompletionService exceptions are never checked > ------------------------------------------------------- > > Key: ISPN-5486 > URL: https://issues.jboss.org/browse/ISPN-5486 > Project: Infinispan > Issue Type: Bug > Components: State Transfer > Affects Versions: 7.2.1.Final > Reporter: William Burns > Assignee: William Burns > Priority: Blocker > Fix For: 7.2.2.Final, 8.0.0.Alpha1 > > > StateConsumerImpl and LocalTopologyManagerImpl both submit tasks to the SemaphoreCompletionService. They drain these tasks, however they never check for any exceptions. This means if there is any kind of exception while running inside this completion service the exception is never displayed anywhere is is silently ignored. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues May 2015