September 2014 - infinispan-issues

[JBoss JIRA] (ISPN-4783) Using new ArrayList<>(resultCache.values())

by Markus Vogt (JIRA)

[ https://issues.jboss.org/browse/ISPN-4783?page=com.atlassian.jira.plugin.... ] Markus Vogt updated ISPN-4783: ------------------------------ Steps to Reproduce: 1. Put a value into a cache 1.1 cache.size() will return 1 2. use new ArrayList<>(cache.values()) 2.1 arraylist.size() will return 2 2.2 2 items can be found in the list was: 1. Put a value into a cache 1.1 cache.size() will return 1 2. use new ArrayList<>(resultCache.values()) 2.1 arraylist.size() will return 2 2.2 2 items can be found in the list > Using new ArrayList<>(resultCache.values()) > ------------------------------------------- > > Key: ISPN-4783 > URL: https://issues.jboss.org/browse/ISPN-4783 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 6.0.2.Final > Reporter: Markus Vogt > Assignee: Dan Berindei > > Hi, > I am a little bit confused about the behaviour of getting the values from a cache and inserting into an ArrayList. > I've putted one value into a cache, so that cache.size() is returning 1. If i now use 'new ArrayList<>(resultCache.values())', there will be two items in the list. > By iterating over the cache, only one iteration will run... Where comes the second item from? > Regards, > Markus -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4783) Using new ArrayList<>(resultCache.values())

by Markus Vogt (JIRA)

Markus Vogt created ISPN-4783: --------------------------------- Summary: Using new ArrayList<>(resultCache.values()) Key: ISPN-4783 URL: https://issues.jboss.org/browse/ISPN-4783 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 6.0.2.Final Reporter: Markus Vogt Assignee: Dan Berindei Hi, I am a little bit confused about the behaviour of getting the values from a cache and inserting into an ArrayList. I've putted one value into a cache, so that cache.size() is returning 1. If i now use 'new ArrayList<>(resultCache.values())', there will be two items in the list. By iterating over the cache, only one iteration will run... Where comes the second item from? Regards, Markus -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4734) Hot Rod marshaller for custom events...etc, needs to be configurable in server

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-4734?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-4734: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2913 > Hot Rod marshaller for custom events...etc, needs to be configurable in server > ------------------------------------------------------------------------------ > > Key: ISPN-4734 > URL: https://issues.jboss.org/browse/ISPN-4734 > Project: Infinispan > Issue Type: Enhancement > Affects Versions: 7.0.0.Beta2 > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 7.0.0.CR1 > > > The marshaller used by Hot Rod to marshall custom events is configurable via HotRodServerConfigurationBuilder. This needs to be extended to server side configuration. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4731) Update classpath to ensure Weld loads Guava instead of Google Collections

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4731?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-4731: ------------------------------- Status: Pull Request Sent (was: Reopened) Git Pull Request: https://github.com/infinispan/infinispan/pull/2878, https://github.com/infinispan/infinispan/pull/2896 (was: https://github.com/infinispan/infinispan/pull/2878) > Update classpath to ensure Weld loads Guava instead of Google Collections > ------------------------------------------------------------------------- > > Key: ISPN-4731 > URL: https://issues.jboss.org/browse/ISPN-4731 > Project: Infinispan > Issue Type: Bug > Components: CDI Integration, Integration > Affects Versions: 7.0.0.Beta2 > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Labels: maven > Fix For: 7.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4731) Update classpath to ensure Weld loads Guava instead of Google Collections

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4731?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-4731: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Update classpath to ensure Weld loads Guava instead of Google Collections > ------------------------------------------------------------------------- > > Key: ISPN-4731 > URL: https://issues.jboss.org/browse/ISPN-4731 > Project: Infinispan > Issue Type: Bug > Components: CDI Integration, Integration > Affects Versions: 7.0.0.Beta2 > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Labels: maven > Fix For: 7.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4782) Server should use FORK instead of a Mux block

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-4782: ------------------------------------- Summary: Server should use FORK instead of a Mux block Key: ISPN-4782 URL: https://issues.jboss.org/browse/ISPN-4782 Project: Infinispan Issue Type: Enhancement Components: Server Affects Versions: 7.0.0.Beta2 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 7.0.0.CR1 The server jgroups subsystem uses a MuxChannel to multiplex messages to different consumers on the same channel. We should use the FORK protocol instead since it has many advantages (i.e. it is what WildFly uses, it doesn't "dirty" the channel). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4620) Add partition handling configuration in the server

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-4620?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-4620: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 7.0.0.Final Resolution: Done > Add partition handling configuration in the server > -------------------------------------------------- > > Key: ISPN-4620 > URL: https://issues.jboss.org/browse/ISPN-4620 > Project: Infinispan > Issue Type: Enhancement > Components: Server > Affects Versions: 7.0.0.Beta1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Labels: partition_handling > Fix For: 7.0.0.CR1, 7.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4633) Local transaction not removed from transaction table after a size() operation

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-4633?page=com.atlassian.jira.plugin.... ] Work on ISPN-4633 started by Adrian Nistor. ------------------------------------------- > Local transaction not removed from transaction table after a size() operation > ----------------------------------------------------------------------------- > > Key: ISPN-4633 > URL: https://issues.jboss.org/browse/ISPN-4633 > Project: Infinispan > Issue Type: Bug > Components: Transactions > Affects Versions: 7.0.0.Beta1 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.0.0.CR1 > > > Executing cache.size() as the only operation during a transaction will leave behind a LocalTransaction in the transaction table. This tx has not locked keys and will eventually be removed by the reaper after a while. The same fix as for ISPN-4196 should be applied for size(). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4781) CustomFailurePolicy.init is never called.

by Duncan Doyle (JIRA)

[ https://issues.jboss.org/browse/ISPN-4781?page=com.atlassian.jira.plugin.... ] Duncan Doyle updated ISPN-4781: ------------------------------- Description: The CustomFailurePolicy interface provides an "init(Cache<K, V> cache)" method, which, according to the JavaDoc, should be invoked during the initialization phase. The method is however never called and my custom XSite failure policy is this never initiated. It seems that the BackupSenderImpl class initiates the CustomFailurePolicy in its 'start()' method does not call the 'init(Cache<K,V> cache)' method of the failure policy. was: The CustomFailurePolicy interface provides an "init(Cache<K, V> cache)" method, which, according to the JavaDoc, should be invoked during the initialization phase. The method is however never called and by custom XSite failure policy is this never initiated. It seems that the BackupSenderImpl class initiates the CustomFailurePolicy in its 'start()' method does not call the 'init(Cache<K,V> cache)' method of the failure policy. > CustomFailurePolicy.init is never called. > ----------------------------------------- > > Key: ISPN-4781 > URL: https://issues.jboss.org/browse/ISPN-4781 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.0.0.Beta2 > Environment: Mac OS X 10.9.4, Oracle HotSpot 1.7.0_67 > Reporter: Duncan Doyle > Assignee: Duncan Doyle > > The CustomFailurePolicy interface provides an "init(Cache<K, V> cache)" method, which, according to the JavaDoc, should be invoked during the initialization phase. The method is however never called and my custom XSite failure policy is this never initiated. > It seems that the BackupSenderImpl class initiates the CustomFailurePolicy in its 'start()' method does not call the 'init(Cache<K,V> cache)' method of the failure policy. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4781) CustomFailurePolicy.init is never called.

by Duncan Doyle (JIRA)

[ https://issues.jboss.org/browse/ISPN-4781?page=com.atlassian.jira.plugin.... ] Duncan Doyle updated ISPN-4781: ------------------------------- Description: The CustomFailurePolicy interface provides an "init(Cache<K, V> cache)" method, which, according to the JavaDoc, should be invoked during the initialization phase. The method is however never called and my custom XSite failure policy is this never initiated. It seems that the BackupSenderImpl class initiates the CustomFailurePolicy in its 'start()' method and does not call the 'init(Cache<K,V> cache)' method of the failure policy. was: The CustomFailurePolicy interface provides an "init(Cache<K, V> cache)" method, which, according to the JavaDoc, should be invoked during the initialization phase. The method is however never called and my custom XSite failure policy is this never initiated. It seems that the BackupSenderImpl class initiates the CustomFailurePolicy in its 'start()' method does not call the 'init(Cache<K,V> cache)' method of the failure policy. > CustomFailurePolicy.init is never called. > ----------------------------------------- > > Key: ISPN-4781 > URL: https://issues.jboss.org/browse/ISPN-4781 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.0.0.Beta2 > Environment: Mac OS X 10.9.4, Oracle HotSpot 1.7.0_67 > Reporter: Duncan Doyle > Assignee: Duncan Doyle > > The CustomFailurePolicy interface provides an "init(Cache<K, V> cache)" method, which, according to the JavaDoc, should be invoked during the initialization phase. The method is however never called and my custom XSite failure policy is this never initiated. > It seems that the BackupSenderImpl class initiates the CustomFailurePolicy in its 'start()' method and does not call the 'init(Cache<K,V> cache)' method of the failure policy. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 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 September 2014