May 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6499) Indexing property is shown as [object Object]

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-6499?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-6499: -------------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.Alpha3 Resolution: Done > Indexing property is shown as [object Object] > --------------------------------------------- > > Key: ISPN-6499 > URL: https://issues.jboss.org/browse/ISPN-6499 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Martin Vrabel > Assignee: Ryan Emerson > Fix For: 9.0.0.Alpha3 > > > if cache has a indexing property e.g. > <indexing> > <property name="default.directory_provider">ram</property> > </indexing> > then in cache configuration -> indexing -> "Indexing Properties" is [object Object] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6500) can't edit indexing properties in console

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-6500?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-6500: -------------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.Alpha3 Resolution: Done > can't edit indexing properties in console > ----------------------------------------- > > Key: ISPN-6500 > URL: https://issues.jboss.org/browse/ISPN-6500 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Martin Vrabel > Assignee: Ryan Emerson > Fix For: 9.0.0.Alpha3 > > > in cache configuration -> indexing -> indexing properties if I edit the filed to e.g. [default.directory_provider ram] -> click update. then If I check if indexing properties was changed, the field is blank. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6529) Not possible to manage cache backups in cache configuration page

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-6529?page=com.atlassian.jira.plugin.... ] Ryan Emerson resolved ISPN-6529. -------------------------------- Fix Version/s: 9.0.0.Alpha2 Resolution: Done > Not possible to manage cache backups in cache configuration page > ---------------------------------------------------------------- > > Key: ISPN-6529 > URL: https://issues.jboss.org/browse/ISPN-6529 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Martin Vrabel > Assignee: Vladimir Blagojevic > Fix For: 9.0.0.Alpha2 > > > cache container -> cache -> cache configuration -> backups tab > The configured cache backups are not shown / are not editable. > after editing something in this backup tab e.g. enable backup a new backup with no sites and name "Backup" is created -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6529) Not possible to manage cache backups in cache configuration page

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-6529?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-6529: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan-management-console/pull/93 > Not possible to manage cache backups in cache configuration page > ---------------------------------------------------------------- > > Key: ISPN-6529 > URL: https://issues.jboss.org/browse/ISPN-6529 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Martin Vrabel > Assignee: Vladimir Blagojevic > > cache container -> cache -> cache configuration -> backups tab > The configured cache backups are not shown / are not editable. > after editing something in this backup tab e.g. enable backup a new backup with no sites and name "Backup" is created -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6590) Defining a cache with non-existent custom store should throw a better exception

by Jakub Markos (JIRA)

Jakub Markos created ISPN-6590: ---------------------------------- Summary: Defining a cache with non-existent custom store should throw a better exception Key: ISPN-6590 URL: https://issues.jboss.org/browse/ISPN-6590 Project: Infinispan Issue Type: Enhancement Components: Loaders and Stores, Server Reporter: Jakub Markos Priority: Minor With current master, if you add this to the default standalone.xml configuration: {code}<local-cache name="mycache" start="EAGER"> <store class="org.infinispan.persistence.None" shared="true" passivation="false"/> </local-cache>{code} the server start hangs, and after 1 minute throws {code}17:28:00,489 ERROR [org.jboss.as.clustering.infinispan] (MSC service thread 1-5) Could not get Custom Cache Store metadata (org.infinispan.persistence.None) within given time.: java.util.concurrent.TimeoutException at java.util.concurrent.CompletableFuture.timedGet(CompletableFuture.java:1771) at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1915) at org.jboss.as.clustering.infinispan.cs.factory.DeployedCacheStoreFactory.createInstance(DeployedCacheStoreFactory.java:34) at org.infinispan.persistence.factory.CacheStoreFactoryRegistry.createInstance(CacheStoreFactoryRegistry.java:39) at org.infinispan.persistence.manager.PersistenceManagerImpl.createLoadersAndWriters(PersistenceManagerImpl.java:534) at org.infinispan.persistence.manager.PersistenceManagerImpl.start(PersistenceManagerImpl.java:130) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:168) at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:864) at org.infinispan.factories.AbstractComponentRegistry.invokeStartMethods(AbstractComponentRegistry.java:633) at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:622) at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:547) at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:238) at org.infinispan.cache.impl.CacheImpl.start(CacheImpl.java:891) at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:634) at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:585) at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:451) at org.infinispan.manager.impl.AbstractDelegatingEmbeddedCacheManager.getCache(AbstractDelegatingEmbeddedCacheManager.java:133) at org.infinispan.server.infinispan.SecurityActions$5.run(SecurityActions.java:131) at org.infinispan.server.infinispan.SecurityActions$5.run(SecurityActions.java:128) at org.infinispan.security.Security.doPrivileged(Security.java:76) at org.infinispan.server.infinispan.SecurityActions.doPrivileged(SecurityActions.java:64) at org.infinispan.server.infinispan.SecurityActions.startCache(SecurityActions.java:136) at org.jboss.as.clustering.infinispan.subsystem.CacheService.start(CacheService.java:86) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) {code} I think we could throw something more specific. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPRK-22) InfinispanRDD is not fault tolerant

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPRK-22?page=com.atlassian.jira.plugin.s... ] Gustavo Fernandes reassigned ISPRK-22: -------------------------------------- Assignee: Gustavo Fernandes > InfinispanRDD is not fault tolerant > ----------------------------------- > > Key: ISPRK-22 > URL: https://issues.jboss.org/browse/ISPRK-22 > Project: Infinispan Spark > Issue Type: Bug > Components: RDD > Affects Versions: 0.3 > Reporter: Vojtech Juranek > Assignee: Gustavo Fernandes > > When primary ISPN server fails during processing InfinispanRDD, Spark is not able to overcome this failure. > This is caused by re-creating {{RemoteCachManager}} with pre-configured ISPN server address (for read [here|https://github.com/infinispan/infinispan-spark/blob/master/src/main/...], for writes [here|https://github.com/infinispan/infinispan-spark/blob/master/src/main/...]), so when this server fails during RDD processing and Spark calls some function, which under the hood creates {{RemoteCacheManager}}, it will fail with connection refused exception. > [Here|https://github.com/vjuranek/infinispan-spark/commit/9aef6b7269feadb9...] are some basic tests (requires some more work, but should be fine for reproducing the issue) and example of exception thrown by HR client: > {noformat} > org.infinispan.client.hotrod.exceptions.TransportException:: Could not fetch transport > at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory.borrowTransportFromPool(TcpTransportFactory.java:395) > at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory.getTransport(TcpTransportFactory.java:241) > at org.infinispan.client.hotrod.impl.operations.FaultTolerantPingOperation.getTransport(FaultTolerantPingOperation.java:26) > at org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:53) > at org.infinispan.client.hotrod.impl.RemoteCacheImpl.ping(RemoteCacheImpl.java:490) > at org.infinispan.client.hotrod.impl.RemoteCacheImpl.resolveCompatibility(RemoteCacheImpl.java:551) > at org.infinispan.client.hotrod.RemoteCacheManager.createRemoteCache(RemoteCacheManager.java:341) > at org.infinispan.client.hotrod.RemoteCacheManager.getCache(RemoteCacheManager.java:222) > at org.infinispan.client.hotrod.RemoteCacheManager.getCache(RemoteCacheManager.java:217) > at org.infinispan.spark.rdd.InfinispanRDD$$anonfun$1.apply(InfinispanRDD.scala:52) > at org.infinispan.spark.rdd.InfinispanRDD$$anonfun$1.apply(InfinispanRDD.scala:52) > at scala.Option.map(Option.scala:146) > at org.infinispan.spark.rdd.InfinispanRDD.compute(InfinispanRDD.scala:52) > at org.infinispan.spark.rdd.InfinispanRDD.compute(InfinispanRDD.scala:66) > at org.apache.spark.rdd.RDD.computeOrReadCheckpoint(RDD.scala:306) > at org.apache.spark.rdd.RDD.iterator(RDD.scala:270) > at org.apache.spark.scheduler.ResultTask.runTask(ResultTask.scala:66) > at org.apache.spark.scheduler.Task.run(Task.scala:89) > at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:213) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: org.infinispan.client.hotrod.exceptions.TransportException:: Could not connect to server: /127.0.0.1:11222 > at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransport.<init>(TcpTransport.java:78) > at org.infinispan.client.hotrod.impl.transport.tcp.TransportObjectFactory.makeObject(TransportObjectFactory.java:35) > at org.infinispan.client.hotrod.impl.transport.tcp.TransportObjectFactory.makeObject(TransportObjectFactory.java:16) > at org.apache.commons.pool.impl.GenericKeyedObjectPool.borrowObject(GenericKeyedObjectPool.java:1220) > at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory.borrowTransportFromPool(TcpTransportFactory.java:390) > ... 21 more > Caused by: java.net.ConnectException: Connection refused > at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) > at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717) > at sun.nio.ch.SocketAdaptor.connect(SocketAdaptor.java:111) > at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransport.<init>(TcpTransport.java:68) > ... 25 more > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6529) Not possible to manage cache backups in cache configuration page

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-6529?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-6529: -------------------------------------- Status: Open (was: New) > Not possible to manage cache backups in cache configuration page > ---------------------------------------------------------------- > > Key: ISPN-6529 > URL: https://issues.jboss.org/browse/ISPN-6529 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Martin Vrabel > Assignee: Vladimir Blagojevic > > cache container -> cache -> cache configuration -> backups tab > The configured cache backups are not shown / are not editable. > after editing something in this backup tab e.g. enable backup a new backup with no sites and name "Backup" is created -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5972) Number of entries not working correctly in cache statistics in mgmt console

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-5972?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-5972: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4307 > Number of entries not working correctly in cache statistics in mgmt console > --------------------------------------------------------------------------- > > Key: ISPN-5972 > URL: https://issues.jboss.org/browse/ISPN-5972 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 8.1.0.Beta1 > Reporter: Jiří Holuša > Assignee: Pedro Ruivo > Fix For: 9.0.0.Alpha2 > > > Page: Caches -> select cache container -> select cache. > Configuration of the cache: replicated cache, 2 nodes in the domain > In the "Cache content" tab, there is a field "# Entries" which should probably show number of entries in the cache. When I put 100 entries in the cache, this field shows 200. Given that it's replicated cache, I think what's happening is that it shows numberOfNodes*numberOfEntries, because when I try to put 100 entries with 3 nodes in the domain, the "# Entries" shows 300. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5972) Number of entries not working correctly in cache statistics in mgmt console

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-5972?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-5972: ------------------------------ Fix Version/s: 9.0.0.Alpha2 > Number of entries not working correctly in cache statistics in mgmt console > --------------------------------------------------------------------------- > > Key: ISPN-5972 > URL: https://issues.jboss.org/browse/ISPN-5972 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 8.1.0.Beta1 > Reporter: Jiří Holuša > Assignee: Pedro Ruivo > Fix For: 9.0.0.Alpha2 > > > Page: Caches -> select cache container -> select cache. > Configuration of the cache: replicated cache, 2 nodes in the domain > In the "Cache content" tab, there is a field "# Entries" which should probably show number of entries in the cache. When I put 100 entries in the cache, this field shows 200. Given that it's replicated cache, I think what's happening is that it shows numberOfNodes*numberOfEntries, because when I try to put 100 entries with 3 nodes in the domain, the "# Entries" shows 300. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6587) Eviction type does not chage after reconfiguring in console

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-6587?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-6587: -------------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.Alpha3 Resolution: Done > Eviction type does not chage after reconfiguring in console > ----------------------------------------------------------- > > Key: ISPN-6587 > URL: https://issues.jboss.org/browse/ISPN-6587 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 9.0.0.Alpha1 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.0.0.Alpha3 > > > container -> cache -> configuration -> eviction -> eviction type > "Type" was empty before. > After changing it to COUNT or MEMORY and afterwards open the configuration page again to check if it was changed the "Type" remained empty. > The JMX value was also not changed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues May 2016