July 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-2285) Allow embedding of JGroups configuration in Infinispan XML

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2285?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2285: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > Allow embedding of JGroups configuration in Infinispan XML > ---------------------------------------------------------- > > Key: ISPN-2285 > URL: https://issues.jboss.org/browse/ISPN-2285 > Project: Infinispan > Issue Type: Feature Request > Components: Configuration > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > > When specifying a transport we should allow "embedding" the JGroups XML configuration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2285) Allow embedding of JGroups configuration in Infinispan XML

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2285?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2285: -------------------------------- Priority: Minor (was: Major) > Allow embedding of JGroups configuration in Infinispan XML > ---------------------------------------------------------- > > Key: ISPN-2285 > URL: https://issues.jboss.org/browse/ISPN-2285 > Project: Infinispan > Issue Type: Feature Request > Components: Configuration > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Minor > > When specifying a transport we should allow "embedding" the JGroups XML configuration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3201) Allow listeners to be invoked only by a primary data owner

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3201?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3201: -------------------------------- Priority: Minor (was: Major) > Allow listeners to be invoked only by a primary data owner > ---------------------------------------------------------- > > Key: ISPN-3201 > URL: https://issues.jboss.org/browse/ISPN-3201 > Project: Infinispan > Issue Type: Feature Request > Components: Distributed Cache, Listeners > Affects Versions: 5.3.0.Final > Reporter: Manik Surtani > Assignee: Mircea Markus > Priority: Minor > Labels: leads > Fix For: 6.0.0.Alpha1, 6.0.0.Final > > > Could be a parameter on the annotation, such as {{primaryOnly}} to prevent all replicas from firing updates, such as: > {code} > @Listener(primaryOnly = true) > public class MyListener { ... } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1856) Allow independent configuration of buffer allocation size vs segment chunks maximum size

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-1856?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-1856: -------------------------------- Assignee: Adrian Nistor (was: Sanne Grinovero) > Allow independent configuration of buffer allocation size vs segment chunks maximum size > ---------------------------------------------------------------------------------------- > > Key: ISPN-1856 > URL: https://issues.jboss.org/browse/ISPN-1856 > Project: Infinispan > Issue Type: Enhancement > Components: Lucene Directory > Reporter: Sanne Grinovero > Assignee: Adrian Nistor > Fix For: 6.0.0.Final > > > Especially make sure that we can allocate buffers efficiently when having chunk_size=MAX_INTEGER or other very high values. > Maybe reuse them as well? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3201) Allow listeners to be invoked only by a primary data owner

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3201?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3201: -------------------------------- Fix Version/s: (was: 6.0.0.Final) (was: 6.0.0.Alpha1) > Allow listeners to be invoked only by a primary data owner > ---------------------------------------------------------- > > Key: ISPN-3201 > URL: https://issues.jboss.org/browse/ISPN-3201 > Project: Infinispan > Issue Type: Feature Request > Components: Distributed Cache, Listeners > Affects Versions: 5.3.0.Final > Reporter: Manik Surtani > Assignee: Mircea Markus > Priority: Minor > Labels: leads > > Could be a parameter on the annotation, such as {{primaryOnly}} to prevent all replicas from firing updates, such as: > {code} > @Listener(primaryOnly = true) > public class MyListener { ... } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1748) Allow consistency for concurrent updates when syncCommitPhase=false

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-1748?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-1748: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > Allow consistency for concurrent updates when syncCommitPhase=false > ------------------------------------------------------------------- > > Key: ISPN-1748 > URL: https://issues.jboss.org/browse/ISPN-1748 > Project: Infinispan > Issue Type: Enhancement > Components: Transactions > Affects Versions: 5.1.0.CR4, 5.1.0.FINAL > Reporter: Mircea Markus > Assignee: Mircea Markus > Priority: Optional > Labels: experimental, performace > Attachments: All_PUT.png > > > when syncCommitPhase=false then there is a window of inconsistency in the case multipel tx access the same key at the same time. > This can be avoided by sending the lock release command after the commit command, in the same thread which is async triggered by the TM.commit. > This should be a very important performance buster for default configurations. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2061) Allow configuring transaction time out through infinisapn.xml

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2061?page=com.atlassian.jira.plugin.... ] Mircea Markus resolved ISPN-2061. --------------------------------- Resolution: Won't Fix This is TransactionManager[1] specific configuration and should be available on the TtransactionManager impl rather than on Infinispan. [1] javax.transaction.TransactionManager.setTransactionTimeout() > Allow configuring transaction time out through infinisapn.xml > ------------------------------------------------------------- > > Key: ISPN-2061 > URL: https://issues.jboss.org/browse/ISPN-2061 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration > Affects Versions: 5.1.4.FINAL > Environment: ISPN 5.1.4.Final > Reporter: dex chen > Assignee: Manik Surtani > > Right now, there is no way to configure transaction time out time through infinispan configuration xml. It would be nice to allow a user to configure the timeout using xml file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2061) Allow configuring transaction time out through infinisapn.xml

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2061?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2061: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > Allow configuring transaction time out through infinisapn.xml > ------------------------------------------------------------- > > Key: ISPN-2061 > URL: https://issues.jboss.org/browse/ISPN-2061 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration > Affects Versions: 5.1.4.FINAL > Environment: ISPN 5.1.4.Final > Reporter: dex chen > Assignee: Manik Surtani > > Right now, there is no way to configure transaction time out time through infinispan configuration xml. It would be nice to allow a user to configure the timeout using xml file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2308) Allow SpringCache to be configured to use asynchronous operations

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2308?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2308: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > Allow SpringCache to be configured to use asynchronous operations > ----------------------------------------------------------------- > > Key: ISPN-2308 > URL: https://issues.jboss.org/browse/ISPN-2308 > Project: Infinispan > Issue Type: Feature Request > Components: Spring integration > Reporter: Mircea Markus > Assignee: Mircea Markus > > There is a pull request[1] pending for quite some time(3 months) for this. As there's no activity I'm creating a JIRA and closing the pull request for now. > [1] https://github.com/infinispan/infinispan/pull/1097 > ----------------- > In testing with a cache that was configured to use asynchronous replication, I was seeing some exceptions in my logs about timeout waiting for a lock on a key when doing a put. (It was not frequent - under heavy load testing it was only on a very small percentage of calls to my service) > Since I was using the @Cacheable annotation to do the caching around those method calls - there was no way for me to catch the CacheExceptions that were thrown. This means that these exceptions were resulting in my services returning 500 errors to the client. > Poking around, it seems that using the putAsync method would make the put methods return immediately and any exception would not be in the same thread so it wouldn't matter. > For my use, a put that fails is fine - spring will just put it in the next time if there is no value in the cache. > This pull request creates a configuration parameter on the EmbeddedCacheManagerFactory and EmbeddedRemoteCacheManagerFactory for "useAsynchronousCacheOperations" which, when set to true, will use a SpringAsynchrnousCache to wrap the native cache instead of the default SpringCache. > I added unit tests around this and updated other tests. > In my own load testing environment, I'm no longer seeing the errors related to cache put key lock timeouts and the execution time for my methods has improved in cases when it would have otherwise been blocking waiting for a put. > (this is a new pull request against the 5.1.x branch - although the changes also apply cleanly to the 5.2 branch as that's where I first created them) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2336) Allow basic per-cache access control on endpoints

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2336?page=com.atlassian.jira.plugin.... ] Mircea Markus resolved ISPN-2336. --------------------------------- Fix Version/s: (was: 6.0.0.Final) Resolution: Rejected Let's do it properly once we have ISPN-2640. > Allow basic per-cache access control on endpoints > ------------------------------------------------- > > Key: ISPN-2336 > URL: https://issues.jboss.org/browse/ISPN-2336 > Project: Infinispan > Issue Type: Feature Request > Components: Remote protocols > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Minor > > Currently an endpoint exposes all caches within the configured container as read-write. We need the ability to decide which caches to expose and with which access semantics (read-only / read-write) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 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 July 2013