January 2014 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3229) L1 cache entries should not be passivated

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3229?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3229: -------------------------------- Component/s: L1 (was: Core) > L1 cache entries should not be passivated > ----------------------------------------- > > Key: ISPN-3229 > URL: https://issues.jboss.org/browse/ISPN-3229 > Project: Infinispan > Issue Type: Bug > Components: L1 > Affects Versions: 5.2.6.Final > Reporter: William Burns > Assignee: William Burns > Fix For: 7.0.0.Alpha1 > > Attachments: DistSyncL1PassivationFuncTest.java > > > L1 entries are stored in the same data container as the real entries. These can be evicted which is fine, however we don't want them to be passivated as this could be costly to write/read from the cache store. We should either prevent L1 cache entries from being passivated or have an option to allow for it. > Currently L1 entries are not differentiated from other entries except through the fact that they are mortal, which is used for other operations as well, which means they would need a placeholder of some kind to tell the container this is a L1 entry. -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3229) L1 cache entries should not be passivated

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3229?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3229: -------------------------------- Component/s: Core > L1 cache entries should not be passivated > ----------------------------------------- > > Key: ISPN-3229 > URL: https://issues.jboss.org/browse/ISPN-3229 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 5.2.6.Final > Reporter: William Burns > Assignee: William Burns > Fix For: 7.0.0.Alpha1 > > Attachments: DistSyncL1PassivationFuncTest.java > > > L1 entries are stored in the same data container as the real entries. These can be evicted which is fine, however we don't want them to be passivated as this could be costly to write/read from the cache store. We should either prevent L1 cache entries from being passivated or have an option to allow for it. > Currently L1 entries are not differentiated from other entries except through the fact that they are mortal, which is used for other operations as well, which means they would need a placeholder of some kind to tell the container this is a L1 entry. -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3093) Design remote Map/Reduce functionality in Infinispan

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3093?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3093: -------------------------------- Component/s: Remote protocols > Design remote Map/Reduce functionality in Infinispan > ---------------------------------------------------- > > Key: ISPN-3093 > URL: https://issues.jboss.org/browse/ISPN-3093 > Project: Infinispan > Issue Type: Task > Components: Remote protocols > Reporter: Mircea Markus > Assignee: Mircea Markus > Fix For: 7.0.0.Alpha1 > > -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3336) Extended Statistics check list

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3336?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3336: -------------------------------- Component/s: Core > Extended Statistics check list > ------------------------------ > > Key: ISPN-3336 > URL: https://issues.jboss.org/browse/ISPN-3336 > Project: Infinispan > Issue Type: Task > Components: Core > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Critical > Labels: core > Fix For: 7.0.0.Alpha1 > > > * add documentation > * check for duplicate stats; > * check for not exposed statistics > * try to improve the code (reduce the number of access to the CHM) > * add tests to check if they are exported via JMX correctly > * failing test: OptimisticLockingTxClusterExtendedStatisticLogicTest.testWriteSkewOnNonOwner > * failing test: PessimisticLockingTxClusterExtendedStatisticLogicTest.testDeadlockOnNonOwnerWithRemoteTx -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2324) Add user documentation for NSBT

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2324?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2324: -------------------------------- Component/s: Documentation-Core > Add user documentation for NSBT > -------------------------------- > > Key: ISPN-2324 > URL: https://issues.jboss.org/browse/ISPN-2324 > Project: Infinispan > Issue Type: Feature Request > Components: Documentation-Core > Affects Versions: 5.2.0.Alpha3 > Reporter: Mircea Markus > Assignee: Dan Berindei > Labels: documentation > Fix For: 7.0.0.Alpha1 > > > To be linked from the user guide page:https://docs.jboss.org/author/display/ISPN/User+Guide -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2956) putIfAbsent on Hot Rod Java client doesn't reliably fulfil contract

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2956?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2956: -------------------------------- Component/s: Remote protocols > putIfAbsent on Hot Rod Java client doesn't reliably fulfil contract > ------------------------------------------------------------------- > > Key: ISPN-2956 > URL: https://issues.jboss.org/browse/ISPN-2956 > Project: Infinispan > Issue Type: Bug > Components: Remote protocols > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Priority: Minor > Labels: hotrod-java-client, remote-clients > Fix For: 7.0.0.Alpha1 > > > Hot Rod's putIfAbsent might have issues on some edge cases: > {quote}I want to know whether the putting entry already exists in the remote > cache cluster, or not. > I thought that RemoteCache.putIfAbsent() would be useful for that > purpose, i.e., > {code} > if (remoteCache.putIfAbsent(k,v) == null) { > // new entry. > } else { > // k already exists. > } > {code} > But no. > The putIfAbsent() for new entry may return non-null value, if one of the > server crushed while putting. > The behavior is like the following: > 1. Client do putIfAbsent(k,v). > 2. The server receives the request and sends replication requests to > other servers. If the server crushed before completing replication, some > servers own that (k,v), but others not. > 3. Client receives the error. The putIfAbsent() internally retries the > same request to the next server in the cluster server list. > 4. If the next server owns the (k,v), the putIfAbsent() returns the > replicated (k,v) at the step 2, without any error. > So, putIfAbsent() is not reliable for knowing whether the putting entry > is *exactly* new or not. > Does anyone have any idea/workaround for this purpose?{quote} > A workaround is to do this: > {quote}We got a simple solution, which can be applied to our customer's application. > If each value part of putting (k,v) is unique or contains unique value, > the client can do *double check* wether the entry is new. > {code} > val = System.nanoTime(); // or uuid is also useful. > if ((ret = cache.putIfAbsent(key, val)) == null > || ret.equals(val)) { > // new entry, if the return value is just the same. > } else { > // key already exists. > } > {code} > We are proposing this workaround which almost works fine.{quote} > However, this is a bit of a cludge. > Hot Rod should be improved with an operation that allows a version to be passed when entry is created, instead of relying on the client generating it. -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1599) Split entry locking in Data Lock(s) and Structure Lock(s)

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-1599?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-1599: -------------------------------- Component/s: Core > Split entry locking in Data Lock(s) and Structure Lock(s) > --------------------------------------------------------- > > Key: ISPN-1599 > URL: https://issues.jboss.org/browse/ISPN-1599 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Reporter: Sanne Grinovero > Assignee: Pedro Ruivo > > See mailing list thread: > http://lists.jboss.org/pipermail/infinispan-dev/2011-December/009605.html > http://infinispan.markmail.org/thread/k7sucf5dnuenuuf7 -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3296) Total Order: timeout exceptions are not throw correctly

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3296?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3296: -------------------------------- Component/s: Core > Total Order: timeout exceptions are not throw correctly > ------------------------------------------------------- > > Key: ISPN-3296 > URL: https://issues.jboss.org/browse/ISPN-3296 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Critical > Fix For: 7.0.0.Alpha1, 7.0.0.Final > > > Issues found in Cloud-TM. Check if they happen here and create a JIRA for each of them > * IgnoreExtraResponseFilter is not needed anymore. > * missing argument log message > * TimeoutException, when happens, it is ignored and the transaction is processed normally > * TimeoutException can block the total order chain (all system is blocked!) > * port the testTimeoutCleanup from cloudtm to master -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3707) I tried to access mbeans on a remotely running Jboss AS7 infinispan server using the jconsole.bat from the infinispan Jboss AS7 installation and i am gettign the following error:

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3707?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3707: -------------------------------- Component/s: Server > I tried to access mbeans on a remotely running Jboss AS7 infinispan server using the jconsole.bat from the infinispan Jboss AS7 installation and i am gettign the following error: > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-3707 > URL: https://issues.jboss.org/browse/ISPN-3707 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 6.0.0.CR1 > Reporter: Pra remo > Assignee: Mircea Markus > Labels: jboss > Fix For: 7.0.0.Alpha1 > > > I tried to access mbeans on a remotely running Jboss AS7 infinispan server using the jconsole.bat from the infinispan Jboss AS7 installation and i am gettign the following error: > xception in thread "VMPanel.connect" java.lang.NoClassDefFoundError: org/jboss/logging/Logger > at org.jboss.remotingjmx.RemotingConnectorProvider.<clinit>(RemotingConnectorProvider.java:42) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:247) > at com.sun.jmx.remote.util.Service$LazyIterator.next(Service.java:270) > at javax.management.remote.JMXConnectorFactory.getConnectorAsService(JMXConnectorFactory.java:425) > at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:310) > at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:247) > at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:207) > at sun.tools.jconsole.ProxyClient.tryConnect(ProxyClient.java:336) > at sun.tools.jconsole.ProxyClient.connect(ProxyClient.java:296) > at sun.tools.jconsole.VMPanel$2.run(VMPanel.java:280) > Caused by: java.lang.ClassNotFoundException: org.jboss.logging.Logger > at java.net.URLClassLoader$1.run(URLClassLoader.java:202) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:190) > at java.lang.ClassLoader.loadClass(ClassLoader.java:306) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) > at java.lang.ClassLoader.loadClass(ClassLoader.java:247) > ... 11 more > I used both url's : service:jmx:remoting-jmx://:9999 service:jmx:remoting-jmx://:4447 > C:\Developer\JDK\Java\jdk1.6.0_34\lib\jconsole.jar;C:\Developer\JDK\Java\jdk1.6.0_34\lib\tools.jar;C:\Users\<user>\Downloads\infinispan-server-6.0.0.CR1-bin\infini > span-server-6.0.0.CR1\jboss-modules.jar;C:\Users\<user>\Downloads\infinispan-server-6.0.0.CR1-bin\infinispan-server-6.0.0.CR1\modules\system\layers\base\org\jboss\ > remoting-jmx\main\remoting-jmx-1.1.0.Final.jar;C:\Users\<user>\Downloads\infinispan-server-6.0.0.CR1-bin\infinispan-server-6.0.0.CR1\modules\system\layers\base\org > \jboss\staxmapper\main\staxmapper-1.1.0.Final.jar;C:\Users\<user>\Downloads\infinispan-server-6.0.0.CR1-bin\infinispan-server-6.0.0.CR1\modules\system\layers\base\ > org\jboss\as\protocol\main\jboss-as-protocol-7.2.0.Final.jar;C:\Users\<user>\Downloads\infinispan-server-6.0.0.CR1-bin\infinispan-server-6.0.0.CR1\modules\system\l > ayers\base\org\jboss\dmr\main\jboss-dmr-1.1.6.Final.jar;C:\Users\<user>\Downloads\infinispan-server-6.0.0.CR1-bin\infinispan-server-6.0.0.CR1\modules\system\layers > \base\org\jboss\as\controller-client\main\jboss-as-controller-client-7.2.0.Final.jar;C:\Users\<user>\Downloads\infinispan-server-6.0.0.CR1-bin\infinispan-server-6. > 0.0.CR1\modules\system\layers\base\org\jboss\threads\main\jboss-threads-2.1.0.Fin -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2577) Silence SuspectExceptions

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2577?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2577: -------------------------------- Component/s: Core > Silence SuspectExceptions > ------------------------- > > Key: ISPN-2577 > URL: https://issues.jboss.org/browse/ISPN-2577 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 5.2.0.Beta4, 6.0.0.Final > Reporter: Michal Linhard > Assignee: Dan Berindei > Priority: Critical > Fix For: 7.0.0.Alpha1, 7.0.0.Final > > > There are lots of SuspectExceptions in resilience test run: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EDG6/view/EDG-REPOR... > We managed to keep these under cover for 5.1.x branch. > This is of course a cosmetic problem, but it polutes the log with unnecessary ERRORs. > Parsed logs here: > http://www.qa.jboss.com/~mlinhard/test_results/run54-parsed/ -- 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

11 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2014