December 2014 - infinispan-issues

[JBoss JIRA] (ISPN-5074) Update remote query quickstart with the new annotation driven Protostream marshalling

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5074?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-5074: -------------------------------- Labels: jdg (was: ) > Update remote query quickstart with the new annotation driven Protostream marshalling > ------------------------------------------------------------------------------------- > > Key: ISPN-5074 > URL: https://issues.jboss.org/browse/ISPN-5074 > Project: Infinispan > Issue Type: Task > Components: Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Labels: jdg > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5074) Update remote query quickstart with the new annotation driven Protostream marshalling

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-5074: ----------------------------------- Summary: Update remote query quickstart with the new annotation driven Protostream marshalling Key: ISPN-5074 URL: https://issues.jboss.org/browse/ISPN-5074 Project: Infinispan Issue Type: Task Components: Remote Querying Reporter: Adrian Nistor Assignee: Adrian Nistor -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3602) Cache statistics update differently in library and Client-Server mode

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3602?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3602: ---------------------------------- Fix Version/s: 7.1.0.Beta1 > Cache statistics update differently in library and Client-Server mode > --------------------------------------------------------------------- > > Key: ISPN-3602 > URL: https://issues.jboss.org/browse/ISPN-3602 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 6.0.0.CR1 > Reporter: Jiří Holuša > Assignee: Vladimir Blagojevic > Priority: Minor > Labels: dm > Fix For: 7.1.0.Beta1 > > > When running jdg quickstart carmart ( https://github.com/infinispan/jdg-quickstart/tree/master/carmart ) I noticed interesting thing. > When calling replace() in library mode, the number of stores in cache statistics doesn't change whereas when calling in Client-Server mode, the number of stores increase by 1. > I went deeper into the code and I found out that in CacheMgmtInterceptor, where there are implemented methods for such statistics updates (like for put() ), there isn't implemented method for updating stats for replace() method, so the control flow is just passed. > I think it should be consistent, but I don't know which approach is intended, if either increase by 1 or leave it the same. > If increase is the answer than the solution is simple, implement CacheMgmtInterceptor.visitReplaceCommand(...) the same way as e.g. visitPutKeyValueCommand. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3602) Cache statistics update differently in library and Client-Server mode

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3602?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3602: ---------------------------------- Assignee: Vladimir Blagojevic (was: Mircea Markus) > Cache statistics update differently in library and Client-Server mode > --------------------------------------------------------------------- > > Key: ISPN-3602 > URL: https://issues.jboss.org/browse/ISPN-3602 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 6.0.0.CR1 > Reporter: Jiří Holuša > Assignee: Vladimir Blagojevic > Priority: Minor > Labels: dm > > When running jdg quickstart carmart ( https://github.com/infinispan/jdg-quickstart/tree/master/carmart ) I noticed interesting thing. > When calling replace() in library mode, the number of stores in cache statistics doesn't change whereas when calling in Client-Server mode, the number of stores increase by 1. > I went deeper into the code and I found out that in CacheMgmtInterceptor, where there are implemented methods for such statistics updates (like for put() ), there isn't implemented method for updating stats for replace() method, so the control flow is just passed. > I think it should be consistent, but I don't know which approach is intended, if either increase by 1 or leave it the same. > If increase is the answer than the solution is simple, implement CacheMgmtInterceptor.visitReplaceCommand(...) the same way as e.g. visitPutKeyValueCommand. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3081) JBoss Modules logging produces garbage at the beginning of line

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3081?page=com.atlassian.jira.plugin.... ] Tristan Tarrant closed ISPN-3081. --------------------------------- Resolution: Out of Date > JBoss Modules logging produces garbage at the beginning of line > --------------------------------------------------------------- > > Key: ISPN-3081 > URL: https://issues.jboss.org/browse/ISPN-3081 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 5.3.0.Alpha1, 6.0.0.Final > Reporter: Michal Linhard > Attachments: configs.zip, serverlogs.zip > > > This is what I get on the console when running infinispan-server-5.3.0-SNAPSHOT > {code} > [0m06:38:12,718 INFO [org.jboss.modules] (main) JBoss Modules version 1.2.0.CR1 > [0m[0m06:38:13,282 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA > [0m[0m06:38:13,486 INFO [org.jboss.as] (MSC service thread 1-7) JBAS015899: JBoss Infinispan Server 5.3.0-SNAPSHOT (AS 7.2.0.Final) starting > [0m[31m06:38:14,687 ERROR [org.jboss.as.server] (Controller Boot Thread) JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration > .. > {code} > configuration: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jdg-perf-cs-client-s... > whole logs: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jdg-perf-cs-client-s... -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3743) Silence "IllegalStateException: Default cache is in 'STOPPING' state" exceptions

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3743?page=com.atlassian.jira.plugin.... ] Tristan Tarrant commented on ISPN-3743: --------------------------------------- [~dan.berindei] do you think this would still occur ? If not can you close it ? > Silence "IllegalStateException: Default cache is in 'STOPPING' state" exceptions > -------------------------------------------------------------------------------- > > Key: ISPN-3743 > URL: https://issues.jboss.org/browse/ISPN-3743 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Affects Versions: 6.0.0.Final > Reporter: Dan Berindei > Labels: testsuite_stability > Fix For: 7.1.0.Beta1 > > > When a cache in STOPPING state receives a command, the exception is propagated all the way to the caller: > {noformat} > 09:33:02,005 ERROR (testng-NonTxPutIfAbsentDuringLeaveStressTest:) [UnitTestTestNGListener] Test testNodeLeavingDuringPutIfAbsent(org.infinispan.distribution.rehash.NonTxPutIfAbsentDuringLeaveStressTest) failed. > java.util.concurrent.ExecutionException: org.infinispan.remoting.RemoteException: ISPN000217: Received exception from NodeC-25987, see cause for remote stack trace > at java.util.concurrent.FutureTask.report(FutureTask.java:122) > Caused by: org.infinispan.remoting.RemoteException: ISPN000217: Received exception from NodeC-25987, see cause for remote stack trace > at org.infinispan.remoting.transport.AbstractTransport.checkResponse(AbstractTransport.java:41) > Caused by: org.infinispan.remoting.RemoteException: ISPN000217: Received exception from NodeD-57301, see cause for remote stack trace > at org.infinispan.remoting.transport.AbstractTransport.checkResponse(AbstractTransport.java:41) > Caused by: java.lang.IllegalStateException: Default cache is in 'STOPPING' state and this is an invocation not belonging to an on-going transaction, so it does not accept new invocations. Either restart it or recreate the cache container. > at org.infinispan.interceptors.InvocationContextInterceptor.handleAll(InvocationContextInterceptor.java:93) > {noformat} > This causes random failures in NonTxPutIfAbsentDuringLeaveStressTest.testNodeLeavingDuringPutIfAbsent. > The originator should either ignore the IllegalStateException or wait for a new cache topology and retry the operation, just like it should for SuspectExceptions (ISPN-2577). -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3884) MarshalledValueContextTest fails on IBM6

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-3884?page=com.atlassian.jira.plugin.... ] Martin Gencur commented on ISPN-3884: ------------------------------------- Vojta, do you think we could re-run tests with latest IBM JDK 6 and see if this still happens? > MarshalledValueContextTest fails on IBM6 > ---------------------------------------- > > Key: ISPN-3884 > URL: https://issues.jboss.org/browse/ISPN-3884 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 7.0.0.Alpha1, 7.0.0.Alpha2, 7.0.0.Alpha3, 7.0.0.Alpha4 > Environment: RHEL6, IBM 6 > Reporter: Vojtech Juranek > Assignee: William Burns > Labels: testsuite_stability > > {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 was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5051) Add trait metrics for cache_availability and cluster_availability into RHQ server plugin

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5051?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5051: ----------------------------------------------- Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 1171158|https://bugzilla.redhat.com/show_bug.cgi?id=1171158] from NEW to ASSIGNED > Add trait metrics for cache_availability and cluster_availability into RHQ server plugin > ---------------------------------------------------------------------------------------- > > Key: ISPN-5051 > URL: https://issues.jboss.org/browse/ISPN-5051 > Project: Infinispan > Issue Type: Feature Request > Components: JMX, reporting and management > Affects Versions: 7.1.0.Alpha1 > Reporter: Tomas Sykora > Labels: rhq > > We are missing support for monitoring in JON for cache and cluster availability trait. > https://issues.jboss.org/browse/ISPN-4827 -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3869) Cannot put key with "like" value via CLI

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3869?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3869: ----------------------------------------------- Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 1048142|https://bugzilla.redhat.com/show_bug.cgi?id=1048142] from NEW to ASSIGNED > Cannot put key with "like" value via CLI > ---------------------------------------- > > Key: ISPN-3869 > URL: https://issues.jboss.org/browse/ISPN-3869 > Project: Infinispan > Issue Type: Bug > Components: CLI > Affects Versions: 6.0.1.Final > Reporter: Vitalii Chepeliuk > Assignee: Mircea Markus > Labels: 630 > > Run following commands in CLI > [remoting://localhost:9999/local/default]> put key1 like > line 1:4 no viable alternative at input 'key1' > line 1:9 mismatched input 'like' expecting set null > [remoting://localhost:9999/local/default]> get key1 > null > [remoting://localhost:9999/local/default]> put key1 like1 > [remoting://localhost:9999/local/default]> get key1 > like1 > [remoting://localhost:9999/local/default]> put key1 LIKE > [remoting://localhost:9999/local/default]> get key1 > LIKE > [remoting://localhost:9999/local/default]> put key1 Like > [remoting://localhost:9999/local/default]> get key1 > Like > --- Server log > 10:33:42,290 ERROR [org.infinispan.cli.interpreter.Interpreter] (pool-1-thread-4) ISPN019003: Interpreter error: org.infinispan.cli.interpreter.ParseException: line 1:4 no viable alternative at input 'key1' > line 1:9 mismatched input 'like' expecting set null > at org.infinispan.cli.interpreter.Interpreter.execute(Interpreter.java:145) [infinispan-cli-server-6.0.1.Final-redhat-1.jar:6.0.1.Final-redhat-1] > at sun.reflect.GeneratedMethodAccessor12.invoke(Unknown Source) [:1.7.0_45] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_45] > at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_45] > at org.infinispan.jmx.ResourceDMBean.invoke(ResourceDMBean.java:271) [infinispan-core-6.0.1.Final-redhat-1.jar:6.0.1.Final-redhat-1] > at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) [rt.jar:1.7.0_45] > at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801) [rt.jar:1.7.0_45] > at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.invoke(PluggableMBeanServerImpl.java:527) [jboss-as-jmx-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] > at org.jboss.as.jmx.PluggableMBeanServerImpl.invoke(PluggableMBeanServerImpl.java:263) [jboss-as-jmx-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] > at org.jboss.remotingjmx.protocol.v2.ServerProxy$InvokeHandler.handle(ServerProxy.java:915) > at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1.run(ServerCommon.java:152) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_45] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_45] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45] -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3870) Cannot put negative numbers via CLI

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3870?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3870: ----------------------------------------------- Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 1048154|https://bugzilla.redhat.com/show_bug.cgi?id=1048154] from NEW to ASSIGNED > Cannot put negative numbers via CLI > ----------------------------------- > > Key: ISPN-3870 > URL: https://issues.jboss.org/browse/ISPN-3870 > Project: Infinispan > Issue Type: Bug > Components: CLI > Affects Versions: 6.0.0.Final > Reporter: Vitalii Chepeliuk > > Run following command via CLI > [remoting://localhost:9999/local/default]> put key1 -0.1234567 > [remoting://localhost:9999/local/default]> get key1 > 0.1234567 > [remoting://localhost:9999/local/default]> put key2 -1.1234567 > [remoting://localhost:9999/local/default]> get key2 > 0.1234567 > [remoting://localhost:9999/local/default]> put key3 -1234567 > [remoting://localhost:9999/local/default]> get key3 > 234567 > [remoting://localhost:9999/local/default]> > --- Server log > 10:51:20,267 ERROR [stderr] (pool-1-thread-8) line 1:10 mismatched character '1' expecting '-' > 10:52:23,997 ERROR [stderr] (pool-1-thread-8) line 1:10 mismatched character '0' expecting '-' > 10:52:32,432 ERROR [stderr] (pool-1-thread-8) line 1:10 mismatched character '1' expecting '-' > 10:52:59,252 ERROR [stderr] (pool-1-thread-8) line 1:10 mismatched character '1' expecting '-' -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 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 December 2014