April 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5347) Extend org.infinispan.objectfilter.Matcher to support event types and user context data

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5347?page=com.atlassian.jira.plugin.... ] Work on ISPN-5347 started by Adrian Nistor. ------------------------------------------- > Extend org.infinispan.objectfilter.Matcher to support event types and user context data > --------------------------------------------------------------------------------------- > > Key: ISPN-5347 > URL: https://issues.jboss.org/browse/ISPN-5347 > Project: Infinispan > Issue Type: Feature Request > Components: Embedded Querying > Affects Versions: 7.2.0.Beta2 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.2.0.CR1 > > > The Matcher should accept a user context object and an event type object beside the instance being tested and should pass the user context and event type to the callback of the matching subscriptions. The user context object and event type should be optional. > Also, when subscribing the user should be able to specify an optional event type. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5347) Extend org.infinispan.objectfilter.Matcher to support event types and user context data

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5347?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-5347: -------------------------------- Status: Open (was: New) > Extend org.infinispan.objectfilter.Matcher to support event types and user context data > --------------------------------------------------------------------------------------- > > Key: ISPN-5347 > URL: https://issues.jboss.org/browse/ISPN-5347 > Project: Infinispan > Issue Type: Feature Request > Components: Embedded Querying > Affects Versions: 7.2.0.Beta2 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.2.0.CR1 > > > The Matcher should accept a user context object and an event type object beside the instance being tested and should pass the user context and event type to the callback of the matching subscriptions. The user context object and event type should be optional. > Also, when subscribing the user should be able to specify an optional event type. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5347) Extend org.infinispan.objectfilter.Matcher to support event types and user context data

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-5347: ----------------------------------- Summary: Extend org.infinispan.objectfilter.Matcher to support event types and user context data Key: ISPN-5347 URL: https://issues.jboss.org/browse/ISPN-5347 Project: Infinispan Issue Type: Feature Request Components: Embedded Querying Affects Versions: 7.2.0.Beta2 Reporter: Adrian Nistor Assignee: Adrian Nistor Fix For: 7.2.0.CR1 The Matcher should accept a user context object and an event type object beside the instance being tested and should pass the user context and event type to the callback of the matching subscriptions. The user context object and event type should be optional. Also, when subscribing the user should be able to specify an optional event type. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5159) Make concurrent startup smooth

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5159?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-5159: ------------------------------------ [~rvansa] shouldn't this be a JGroups bug? > Make concurrent startup smooth > ------------------------------ > > Key: ISPN-5159 > URL: https://issues.jboss.org/browse/ISPN-5159 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 7.1.0.Beta1 > Reporter: Radim Vansa > Assignee: Dan Berindei > > When starting many instances in parallel, it often happens that the node does not detect its neighborhood very well and this results in many subclusters, merging views etc. > Merging two available partitions has undefined results (AFAIK). While we can expect that there are no requests to the cluster from the application ^1^, Infinispan itself uses some caches to store internal information (HotRod routing, Protobuf etc...). It would be better if the available-available merge would provide hooks for rebuilding this info. > ^1^) Being able to start the cluster with reads/writes disabled and enable them only when the cache has expected number of members would be convenient, too. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5306) Eviction should allow for long size configuration

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5306?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5306: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3361 > Eviction should allow for long size configuration > ------------------------------------------------- > > Key: ISPN-5306 > URL: https://issues.jboss.org/browse/ISPN-5306 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration, Eviction > Reporter: William Burns > Assignee: William Burns > Fix For: 7.2.0.CR1 > > > We added the new EquivalentBoundedConcurrentHashMapv8 in ISPN-3023. This new implementation allows for long size instead of int. However there is no way to configure these at this time. We need to change both the xsd schema and the programmatic configuration to support long. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5306) Eviction should allow for long size configuration

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5306?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5306: -------------------------------- Status: Open (was: New) > Eviction should allow for long size configuration > ------------------------------------------------- > > Key: ISPN-5306 > URL: https://issues.jboss.org/browse/ISPN-5306 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration, Eviction > Reporter: William Burns > Assignee: William Burns > Fix For: 7.2.0.CR1 > > > We added the new EquivalentBoundedConcurrentHashMapv8 in ISPN-3023. This new implementation allows for long size instead of int. However there is no way to configure these at this time. We need to change both the xsd schema and the programmatic configuration to support long. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5266) Optimize PutAll operations (Hot Rod)

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5266?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5266: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/3352 > Optimize PutAll operations (Hot Rod) > ------------------------------------ > > Key: ISPN-5266 > URL: https://issues.jboss.org/browse/ISPN-5266 > Project: Infinispan > Issue Type: Enhancement > Reporter: Pedro Zapata > Assignee: William Burns > > - PutAll: to ensure that users can load massive amount of data into the grid quickly over Hot Rod. > - Performance improvement over large data sets. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5264) Optimize PutAll operations (library mode)

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5264?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5264: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/3354 > Optimize PutAll operations (library mode) > ----------------------------------------- > > Key: ISPN-5264 > URL: https://issues.jboss.org/browse/ISPN-5264 > Project: Infinispan > Issue Type: Enhancement > Reporter: Pedro Zapata > Assignee: William Burns > > - PutAll: to ensure that users can load massive amount of data into the grid quickly in Library mode > - Performance improvement over large data sets. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5286) JSR-107 Support for clustered caches in HotRod implementation

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5286?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5286: ----------------------------------------------- Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 1200822|https://bugzilla.redhat.com/show_bug.cgi?id=1200822] from ASSIGNED to ON_QA > JSR-107 Support for clustered caches in HotRod implementation > -------------------------------------------------------------- > > Key: ISPN-5286 > URL: https://issues.jboss.org/browse/ISPN-5286 > Project: Infinispan > Issue Type: Bug > Components: JCache > Reporter: Matej Čimbora > Assignee: Ion Savin > > Current implementation supports only using local caches - usage of different cache types leads to the following exceptions (when using cache which is included in configuration file): > Client: > {code} > javax.cache.CacheException: ISPN021027: Failed to add local cache 'default' on the server > at org.infinispan.jcache.remote.ServerManager$3.run(ServerManager.java:118) > at org.infinispan.jcache.remote.ServerManager.withManagementClient(ServerManager.java:171) > at org.infinispan.jcache.remote.ServerManager.addCache(ServerManager.java:104) > at org.infinispan.jcache.remote.JCacheManager.create(JCacheManager.java:65) > at org.infinispan.jcache.AbstractJCacheManager.createCache(AbstractJCacheManager.java:94) > at org.infinispan.server.test.jcache.JCacheRemoteIT.testCachingConfiguration(JCacheRemoteIT.java:78) > {code} > Server: > {code} > 10:47:29,896 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) JBAS014612: Operation ("add") failed - address: ([ > ("subsystem" => "infinispan"), > ("cache-container" => "clustered"), > ("local-cache" => "default") > ]): org.jboss.msc.service.DuplicateServiceException: Service jboss.infinispan.clustered.default.config is already registered > at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) > {code} > Furthermore, when using multiple nodes in the cluster and the cache is not amongst configured caches, it is created as 'local' only on one node (this relates to fact org.infinispan.jcache.remote.ServerManager is configured to use one specific management interface - which is btw hardcoded and cannot be changed). Exception can occur when trying to write into cache. > > Client > {code} > javax.cache.CacheException: ISPN021022: Cache named 'custom' was not found. > at org.infinispan.jcache.remote.JCacheManager.create(JCacheManager.java:75) > at org.infinispan.jcache.AbstractJCacheManager.createCache(AbstractJCacheManager.java:94) > at org.infinispan.server.test.jcache.JCacheRemoteIT.testCachingConfiguration(JCacheRemoteIT.java:78) > {code} > Server > {code} > 10:59:01,034 ERROR [org.infinispan.server.hotrod.HotRodDecoder] (HotRodServerWorker-1) ISPN005003: Exception reported: org.infinispan.server.hotrod.CacheNotFoundException: Cache with name 'custom' not found amongst the configured caches > at org.infinispan.server.hotrod.HotRodDecoder.getCache(HotRodDecoder.scala:102) > {code} > For full logs pease see linked BZ. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5159) Make concurrent startup smooth

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5159?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5159: ---------------------------------- Status: Open (was: New) > Make concurrent startup smooth > ------------------------------ > > Key: ISPN-5159 > URL: https://issues.jboss.org/browse/ISPN-5159 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 7.1.0.Beta1 > Reporter: Radim Vansa > Assignee: Dan Berindei > > When starting many instances in parallel, it often happens that the node does not detect its neighborhood very well and this results in many subclusters, merging views etc. > Merging two available partitions has undefined results (AFAIK). While we can expect that there are no requests to the cluster from the application ^1^, Infinispan itself uses some caches to store internal information (HotRod routing, Protobuf etc...). It would be better if the available-available merge would provide hooks for rebuilding this info. > ^1^) Being able to start the cluster with reads/writes disabled and enable them only when the cache has expected number of members would be convenient, too. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues April 2015