January 2014 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3898) Missing dependencies in infinispan-server-jgroups

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3898?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3898: -------------------------------- Component/s: Server > Missing dependencies in infinispan-server-jgroups > ------------------------------------------------- > > Key: ISPN-3898 > URL: https://issues.jboss.org/browse/ISPN-3898 > Project: Infinispan > Issue Type: Bug > Components: Server > Reporter: Valerio Schiavoni > Assignee: Mircea Markus > Attachments: versions_pom.diff > > > Maven complains about unresolvable dependencies: > [ERROR] Failed to execute goal on project infinispan-server-jgroups: Could not resolve dependencies for project org.infinispan.server:infinispan-server-jgroups:jar:7.0.0-SNAPSHOT: The following artifacts could not be resolved: org.jboss.byteman:byteman:jar:2.0.1, org.jboss.byteman:byteman-submit:jar:2.0.1, org.jboss.byteman:byteman-install:jar:2.0.1: Could not find artifact org.jboss.byteman:byteman:jar:2.0.1 in central > (same happens with the other byteman dependencies). -- 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-3355) Add support for clustered listeners

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3355?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3355: -------------------------------- Component/s: Core > Add support for clustered listeners > ----------------------------------- > > Key: ISPN-3355 > URL: https://issues.jboss.org/browse/ISPN-3355 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Reporter: Mircea Markus > Assignee: William Burns > Fix For: 7.0.0.Final > > > As opposed to the current listener approach in Infinispan ( a listener instance is invoked on the data owners ), this JIRA is about adding support for a cluster listener: the same listener instance that is notified disregarding of data ownership ( RPC calls involved). > Due to the fact that the listener notification might involve an RPC, it is nice to be able to specify filters on these listeners. > The clustered listener support opens the way for some interesting architectures: > * persistent/continuous queries: the query is transformed in a filter. On each notification, the listener (stateful) updates the query state > * simplistic CEP can be built on top of the persistent query described above > * remote/hotrod notifications might be based on clustered listeners 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3933) Preloading and Shared options can not be enabled on a JDBCCachestore via configuration files

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-3933?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-3933: ---------------------------------- Description: The configuration schema doesn't allow to enable the "preload" attribute of a JDBCCacheStore. I classify this as critical as the JDBCCacheStore is the only viable solution for a shared cachestore, and the Lucene Directory requires "preload" to be activated. was: The configuration schema doesn't allow to enable the "preload" attribute of a JDBCCacheStore. I classify this as critical as the JDBCCacheStore is the only viable solution for a shared cachestore, and the Lucene Directory required "preload" to be activated. > Preloading and Shared options can not be enabled on a JDBCCachestore via configuration files > -------------------------------------------------------------------------------------------- > > Key: ISPN-3933 > URL: https://issues.jboss.org/browse/ISPN-3933 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 6.0.0.Final, 6.0.1.Final > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Priority: Critical > Fix For: 7.0.0.Alpha1, 7.0.0.Final > > > The configuration schema doesn't allow to enable the "preload" attribute of a JDBCCacheStore. > I classify this as critical as the JDBCCacheStore is the only viable solution for a shared cachestore, and the Lucene Directory requires "preload" to be activated. -- 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-3905) Murmurhash3 implementation is slow on String keys

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3905?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3905: -------------------------------- Component/s: Core > Murmurhash3 implementation is slow on String keys > ------------------------------------------------- > > Key: ISPN-3905 > URL: https://issues.jboss.org/browse/ISPN-3905 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 6.0.0.Final, 6.0.1.Final > Reporter: Sanne Grinovero > Assignee: Mircea Markus > Fix For: 7.0.0.Final > > > String instances are a common choice for being used as key entries, still the getBytes() operation being performed allocates costly buffers, and the computation to get those bytes looks like expensive too. > I suspect there might be good reasons for not using the String's own hashcode directly as an input to Murmurhash? Still that's what other implementations seem to do. -- 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-3865) How to update individual record inside cached list object??

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3865?page=com.atlassian.jira.plugin.... ] Mircea Markus resolved ISPN-3865. --------------------------------- Resolution: Rejected please use the forums for questions: http://infinispan.org/community/ > How to update individual record inside cached list object?? > ----------------------------------------------------------- > > Key: ISPN-3865 > URL: https://issues.jboss.org/browse/ISPN-3865 > Project: Infinispan > Issue Type: Feature Request > Environment: Infinispan 4.2,jboss5.1 > Reporter: Nishant B > Assignee: Mircea Markus > > hi, i am storing in cache list of objects with a particular key name to that list .So while searching with that key name i am able to get all the objects as a list successfully. But if i have to update a single object record in that list how can i get it from cache and get it updated. > Eg i have car and bike as two different class.While storing in cache ,with key name as 'car' and 'bike' ,i store list of 10 car objects and 10 bike objects. > But to update a single car object within that list..how to retrive it from cache..since in cache the entire list is stored as key 'car'. -- 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-3933) Preloading and Shared options can not be enabled on a JDBCCachestore via configuration files

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-3933?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-3933: ---------------------------------- Summary: Preloading and Shared options can not be enabled on a JDBCCachestore via configuration files (was: Preloading on a JDBCCachestore can not be enabled via configuration files) > Preloading and Shared options can not be enabled on a JDBCCachestore via configuration files > -------------------------------------------------------------------------------------------- > > Key: ISPN-3933 > URL: https://issues.jboss.org/browse/ISPN-3933 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 6.0.0.Final, 6.0.1.Final > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Priority: Blocker > Fix For: 7.0.0.Alpha1, 7.0.0.Final > > > The configuration schema doesn't allow to enable the "preload" attribute of a JDBCCacheStore. > I classify this as critical as the JDBCCacheStore is the only viable solution for a shared cachestore, and the Lucene Directory required "preload" to be activated. -- 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-3879) RHQ management -- server plugin -- two X-Site related operations are failing.

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3879?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3879: -------------------------------- Component/s: JMX, reporting and management > RHQ management -- server plugin -- two X-Site related operations are failing. > ----------------------------------------------------------------------------- > > Key: ISPN-3879 > URL: https://issues.jboss.org/browse/ISPN-3879 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 6.0.1.Final > Reporter: Tomas Sykora > Assignee: Mircea Markus > > The only information I was able to gather until now: > java.lang.Exception: JBAS011002: Failed to invoke operation: null, rolled-back=true > at org.rhq.core.pc.operation.OperationInvocation.run(OperationInvocation.java:278) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:679) -- 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-3884) MarshalledValueContextTest fails on IBM6

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3884?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3884: -------------------------------- Component/s: Test Suite - Core > MarshalledValueContextTest fails on IBM6 > ---------------------------------------- > > Key: ISPN-3884 > URL: https://issues.jboss.org/browse/ISPN-3884 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Environment: RHEL6, IBM 6 > Reporter: Vojtech Juranek > Assignee: William Burns > > {noformat} > java.lang.ArrayStoreException > at java.util.ArrayList.set(ArrayList.java:635) > at org.infinispan.commands.control.LockControlCommand.replaceKey(LockControlCommand.java:84) > at org.infinispan.interceptors.MarshalledValueInterceptor.visitLockControlCommand(MarshalledValueInterceptor.java:91) > at org.infinispan.commands.control.LockControlCommand.acceptVisitor(LockControlCommand.java:110) > at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:98) > at org.infinispan.interceptors.TxInterceptor.invokeNextInterceptorAndVerifyTransaction(TxInterceptor.java:114) > at org.infinispan.interceptors.TxInterceptor.visitLockControlCommand(TxInterceptor.java:181) > at org.infinispan.commands.control.LockControlCommand.acceptVisitor(LockControlCommand.java:110) > at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:98) > at org.infinispan.interceptors.base.CommandInterceptor.handleDefault(CommandInterceptor.java:112) > at org.infinispan.commands.AbstractVisitor.visitLockControlCommand(AbstractVisitor.java:147) > at org.infinispan.commands.control.LockControlCommand.acceptVisitor(LockControlCommand.java:110) > at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:98) > at org.infinispan.context.MarshalledValueContextTest$ContextExtractingInterceptor.handleDefault(MarshalledValueContextTest.java:79) > at org.infinispan.commands.AbstractVisitor.visitLockControlCommand(AbstractVisitor.java:147) > at org.infinispan.commands.control.LockControlCommand.acceptVisitor(LockControlCommand.java:110) > at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:98) > at org.infinispan.interceptors.InvocationContextInterceptor.handleAll(InvocationContextInterceptor.java:110) > at org.infinispan.interceptors.InvocationContextInterceptor.visitLockControlCommand(InvocationContextInterceptor.java:78) > at org.infinispan.commands.control.LockControlCommand.acceptVisitor(LockControlCommand.java:110) > at org.infinispan.interceptors.InterceptorChain.invoke(InterceptorChain.java:333) > at org.infinispan.CacheImpl.lock(CacheImpl.java:656) > at org.infinispan.CacheImpl.lock(CacheImpl.java:639) > at org.infinispan.context.MarshalledValueContextTest.testContentsOfContext(MarshalledValueContextTest.java:52) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) > at java.lang.reflect.Method.invoke(Method.java:611) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:715) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:907) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1237) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) > at org.testng.TestRunner.privateRun(TestRunner.java:767) > at org.testng.TestRunner.run(TestRunner.java:617) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:334) > at org.testng.SuiteRunner.access$000(SuiteRunner.java:37) > at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:368) > at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:314) > at java.util.concurrent.FutureTask.run(FutureTask.java:149) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:906) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:929) > at java.lang.Thread.run(Thread.java:761) > {noformat} -- 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-3076) Infinispan should enable use of log4j2

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3076?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3076: -------------------------------- Component/s: Core > Infinispan should enable use of log4j2 > -------------------------------------- > > Key: ISPN-3076 > URL: https://issues.jboss.org/browse/ISPN-3076 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 5.2.5.Final, 6.0.0.Final > Environment: Any > Reporter: Divya Mehra > Assignee: Mircea Markus > > log4j locks up on a certain amount of load, especially under concurrent access. The recommendation was to move up to log4j2. This can be done by removing > 1 JAR (log4j.jar) and adding 2 JARs (log4j-bridge and log4j-core.jar). > Also refer: https://issues.jboss.org/browse/ISPN-2976 -- 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-3933) Preloading and Shared options can not be enabled on a JDBCCachestore via configuration files

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-3933?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-3933: ---------------------------------- Priority: Critical (was: Blocker) > Preloading and Shared options can not be enabled on a JDBCCachestore via configuration files > -------------------------------------------------------------------------------------------- > > Key: ISPN-3933 > URL: https://issues.jboss.org/browse/ISPN-3933 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 6.0.0.Final, 6.0.1.Final > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Priority: Critical > Fix For: 7.0.0.Alpha1, 7.0.0.Final > > > The configuration schema doesn't allow to enable the "preload" attribute of a JDBCCacheStore. > I classify this as critical as the JDBCCacheStore is the only viable solution for a shared cachestore, and the Lucene Directory required "preload" to be activated. -- 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