April 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5350) Use DSL based filters with Hot Rod event listeners

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5350?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-5350: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1211944 > Use DSL based filters with Hot Rod event listeners > -------------------------------------------------- > > Key: ISPN-5350 > URL: https://issues.jboss.org/browse/ISPN-5350 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Protocols > Affects Versions: 7.2.0.Beta2 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.2.0.CR1, 7.2.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5349) Use DSL based filters with local and clustered event listeners

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5349?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-5349: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1211944 > Use DSL based filters with local and clustered event listeners > -------------------------------------------------------------- > > Key: ISPN-5349 > URL: https://issues.jboss.org/browse/ISPN-5349 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Affects Versions: 7.2.0.Beta2 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.2.0.CR1, 7.2.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5234) Implement single cluster view page (P1)

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5234?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5234: ---------------------------------- Status: Open (was: New) > Implement single cluster view page (P1) > --------------------------------------- > > Key: ISPN-5234 > URL: https://issues.jboss.org/browse/ISPN-5234 > Project: Infinispan > Issue Type: Task > Components: JMX, reporting and management > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Fix For: 8.0.0.Final > > > In our admin console current single cluster view page does not contain the following functionality that should be implemented: > * -Zoom in/out- > * Node availability/detail > * Filter by metrics (node view) > * Filter by metrics (cache view) > * Search node (search as you type) > * Search cache (search as you type) > * -Cluster switcher- > * Cluster status view -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5234) Implement single cluster view page (P1)

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5234?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5234: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan-management-console/pull/6, https://github.com/infinispan/infinispan-management-console/pull/7, https://github.com/infinispan/infinispan-management-console/pull/9 (was: https://github.com/infinispan/infinispan-management-console/pull/6, https://github.com/infinispan/infinispan-management-console/pull/7) > Implement single cluster view page (P1) > --------------------------------------- > > Key: ISPN-5234 > URL: https://issues.jboss.org/browse/ISPN-5234 > Project: Infinispan > Issue Type: Task > Components: JMX, reporting and management > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Fix For: 8.0.0.Final > > > In our admin console current single cluster view page does not contain the following functionality that should be implemented: > * -Zoom in/out- > * Node availability/detail > * Filter by metrics (node view) > * Filter by metrics (cache view) > * Search node (search as you type) > * Search cache (search as you type) > * -Cluster switcher- > * Cluster status view -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5321) StringBasedStoreMultinodeIT.testFetchState fails randomly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5321?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5321: ----------------------------------------------- Sebastian Łaskawiec <slaskawi(a)redhat.com> changed the Status of [bug 1210312|https://bugzilla.redhat.com/show_bug.cgi?id=1210312] from POST to MODIFIED > StringBasedStoreMultinodeIT.testFetchState fails randomly > --------------------------------------------------------- > > Key: ISPN-5321 > URL: https://issues.jboss.org/browse/ISPN-5321 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Reporter: Vojtech Juranek > Assignee: Vojtech Juranek > Fix For: 7.2.0.Beta2 > > > Fails as {{k1}} enrtyr is evicted instead of expected {{k2}}: > {noformat} > java.lang.AssertionError: expected null, but was:<[B@636e6f73> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotNull(Assert.java:664) > at org.junit.Assert.assertNull(Assert.java:646) > at org.junit.Assert.assertNull(Assert.java:656) > at org.infinispan.server.test.cs.jdbc.multinode.StringBasedStoreMultinodeIT.testFetchState(StringBasedStoreMultinodeIT.java:60) > {noformat} > see e.g. [this CI build|http://ci.infinispan.org/viewLog.html?buildId=24519&tab=buildResult...] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5375) Some CLI commands (evict, rm) are not codec-aware

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5375?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-5375: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Some CLI commands (evict, rm) are not codec-aware > ------------------------------------------------- > > Key: ISPN-5375 > URL: https://issues.jboss.org/browse/ISPN-5375 > Project: Infinispan > Issue Type: Bug > Components: CLI > Affects Versions: 7.2.0.Beta2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 7.2.0.CR1, 7.2.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5365) JmxManagementIT.testCacheStatisticsAttributes always fails

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5365?page=com.atlassian.jira.plugin.... ] Galder Zamarreño resolved ISPN-5365. ------------------------------------ Fix Version/s: 7.2.0.Final Resolution: Done > JmxManagementIT.testCacheStatisticsAttributes always fails > ----------------------------------------------------------- > > Key: ISPN-5365 > URL: https://issues.jboss.org/browse/ISPN-5365 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 7.2.0.Beta2 > Reporter: Dan Berindei > Assignee: Vladimir Blagojevic > Priority: Blocker > Labels: testsuite_stability > Fix For: 7.2.0.CR1, 7.2.0.Final > > > Looks like the {{ElapsedTime}} attribute got renamed to {{TimeSinceStart}}, and {{JmxManagementIT}} still uses the old name: > {noformat} > javax.management.AttributeNotFoundException: Unknown attribute 'ElapsedTime'. Known attributes names are: [numberOfEntries, averageReadTime, hitRatio, timeSinceReset, averageRemoveTime, misses, evictions, readWriteRatio, statisticsEnabled, hits, timeSinceStart, removeMisses, removeHits, stores, averageWriteTime] > at org.infinispan.jmx.ResourceDMBean.getAttribute(ResourceDMBean.java:181) > at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:647) > at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:678) > at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.getAttribute(PluggableMBeanServerImpl.java:1377) > at org.jboss.as.jmx.PluggableMBeanServerImpl.getAttribute(PluggableMBeanServerImpl.java:384) > at org.jboss.remotingjmx.protocol.v2.ServerProxy$GetAttributeHandler.handle(ServerProxy.java:691) > at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1$1.run(ServerCommon.java:153) > at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor$1.run(ServerInterceptorFactory.java:75) > at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor$1.run(ServerInterceptorFactory.java:70) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:415) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:94) > at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor.handleEvent(ServerInterceptorFactory.java:70) > at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1.run(ServerCommon.java:149) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > {noformat} > I think maybe we should keep the old attribute name as well, for backwards compatibility. I'm thinking RHQ might use it... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5147) Creation/configuration of caches should not require a server restart

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5147?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-5147: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 7.2.0.CR1 Resolution: Done > Creation/configuration of caches should not require a server restart > -------------------------------------------------------------------- > > Key: ISPN-5147 > URL: https://issues.jboss.org/browse/ISPN-5147 > Project: Infinispan > Issue Type: Enhancement > Components: JMX, reporting and management, Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 7.2.0.CR1, 7.2.0.Final > > > When creating a cache using the management interface, we want to be able to set all specific configuration and start the cache without requiring a server restart. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5376) Sync remote events

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-5376: -------------------------------------- Summary: Sync remote events Key: ISPN-5376 URL: https://issues.jboss.org/browse/ISPN-5376 Project: Infinispan Issue Type: Enhancement Components: Remote Protocols Reporter: Galder Zamarreño Priority: Minor The current remote events are async in the sense that the server fires them and there's no acknowledgement from the client that it's consumed them. Async enables reasonably performant remote events while handling server failures via the include current state options for when a failover is discovered. Some applications however demand that the event is guaranteed to be fired before the cache operation has finished. Having to do remote sync events would be hurt performance considerably but there are situations when this is needed, e.g. the JCache TCK. The remote JCache implementation is including some logic to deal with this, but it might be better to implement this directly in the Hot Rod protocol in the future. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4751) Hibernate search, infinispan and Amazon S3 - IllegalArgumentException: bucketId: A96137216.bz2 (expected: integer)

by George Christman (JIRA)

[ https://issues.jboss.org/browse/ISPN-4751?page=com.atlassian.jira.plugin.... ] George Christman commented on ISPN-4751: ---------------------------------------- Hi Sanne, could you elaborate a little bit more on how I would go about getting a Lucene Directory module from Infinispan to support Lucene v3? If it's not to difficult, that might be my quickest approach at getting all this up and working while we wait for the Faceting upgrades to be completed. Again thanks. > Hibernate search, infinispan and Amazon S3 - IllegalArgumentException: bucketId: A96137216.bz2 (expected: integer) > ------------------------------------------------------------------------------------------------------------------ > > Key: ISPN-4751 > URL: https://issues.jboss.org/browse/ISPN-4751 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Reporter: Lance Ess > Assignee: Vojtech Juranek > > I'm trying to use hibernate-search to host a Lucene index on Amazon S3 but I'm getting the following exception: > {code} > Exception in thread "LuceneIndexesData-CloudCacheStore-0" java.lang.IllegalArgumentException: bucketId: A96137216.bz2 (expected: integer) > at org.infinispan.loaders.bucket.Bucket.setBucketId(Bucket.java:84) > at org.infinispan.loaders.cloud.CloudCacheStore.readFromBlob(CloudCacheStore.java:450) > at org.infinispan.loaders.cloud.CloudCacheStore.scanBlobForExpiredEntries(CloudCacheStore.java:292) > at org.infinispan.loaders.cloud.CloudCacheStore.purge(CloudCacheStore.java:284) > at org.infinispan.loaders.cloud.CloudCacheStore.purgeInternal(CloudCacheStore.java:336) > at org.infinispan.loaders.AbstractCacheStore$2.run(AbstractCacheStore.java:111) > at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) > at java.lang.Thread.run(Unknown Source) > {code} > The documentation for persisting Lucene indexes on Amazon-S3 is a little sparse but I think I'm on the right track. I'm trying to start infinispan embedded within my application so I've specified a path to the infinispan XML as follows in my hibernate.cfg.xml > {code:xml} > <property name="hibernate.search.default.directory_provider">infinispan</property> > <property name="hibernate.search.infinispan.configuration_resourcename">infinispan-amazons3.xml</property> > <property name="hibernate.search.infinispan.chunk_size">300000000</property> > {code} > And my infinispan-amazons3.xml is: > {code:xml} > <infinispan> > <default> > <loaders> > <cloudStore xmlns="urn:infinispan:config:cloud:5.3" > cloudService="aws-s3" > identity="user" > password="password" > bucketPrefix="bucket"> > </cloudStore> > </loaders> > </default> > </infinispan> > {code} > I'm using the following versions (maven pom.xml) > {code} > <dependency> > <groupId>org.hibernate</groupId> > <artifactId>hibernate-search</artifactId> > <version>4.4.4.Final</version> > </dependency> > <dependency> > <groupId>org.hibernate</groupId> > <artifactId>hibernate-search-infinispan</artifactId> > <version>4.4.4.Final</version> > </dependency> > <dependency> > <groupId>org.infinispan</groupId> > <artifactId>infinispan-cachestore-cloud</artifactId> > <version>5.3.0.Final</version> > </dependency> > <dependency> > <groupId>org.jclouds.provider</groupId> > <artifactId>aws-s3</artifactId> > <version>1.4.1</version> > </dependency> > {code} > I initially thought this was related to ISPN-1909 but my version is after the fix for that issue (5.1.3.CR1, 5.1.3.FINAL) > FYI here's my maven dependency tree (grepped for infinispan) > {code} > $ mvn dependency:tree | grep infinispan > [INFO] +- org.hibernate:hibernate-search-infinispan:jar:4.4.4.Final:compile > [INFO] | \- org.infinispan:infinispan-lucene-directory:jar:5.3.0.Final:compile > [INFO] +- org.infinispan:infinispan-cachestore-cloud:jar:5.3.0.Final:compile > [INFO] | \- org.infinispan:infinispan-core:jar:5.3.0.Final:compile > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues April 2015