[JBoss JIRA] (ISPN-871) Out-of-heap data container implementation
by Ben Cotton (JIRA)
[ https://issues.jboss.org/browse/ISPN-871?page=com.atlassian.jira.plugin.s... ]
Ben Cotton commented on ISPN-871:
---------------------------------
Was this ever done?
If so, is it documented how to configure an off-heap Cache in a specific ISPN version?
If not, I would recommend the consideration of Peter Lawrey's OpenHFT Chronocle net.openhft.collections.HugeHashMap implementation ... which is based on a off-heap MappedByteBuffer onto any/all of (/dev/shm, tmpfs, ext4) and is exceedingly high performant.
https://github.com/OpenHFT/HugeCollections
> Out-of-heap data container implementation
> -----------------------------------------
>
> Key: ISPN-871
> URL: https://issues.jboss.org/browse/ISPN-871
> Project: Infinispan
> Issue Type: Feature Request
> Components: Configuration
> Reporter: Manik Surtani
> Assignee: Tristan Tarrant
> Labels: gc, jni, native, performance, research
>
> The {{DataContainer}} interface could be implemented using a off-heap impl in C, using a wrapper around [TBB|http://threadingbuildingblocks.org/]'s concurrent hashmap.
> Cheap and easy way, no memory management needed, at worst case same performance as the Java CHM-like impl of the data container + some JNI overhead. Potential benefit of large data heaps.
--
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
[JBoss JIRA] (ISPN-3076) Infinispan should enable use of log4j2
by Radim Vansa (JIRA)
[ https://issues.jboss.org/browse/ISPN-3076?page=com.atlassian.jira.plugin.... ]
Radim Vansa commented on ISPN-3076:
-----------------------------------
I think that in production the INFO level should be used as the threshold, and log4j can handle that.
When debugging (tracing), I've experienced contention in log4j locks for many times, and this contention led to node unresponsiveness and consequential failure.
Log4j2 is not complete cure for that, but it eliminates the bottleneck in logging framework and leaves us only in synchronization when persisting the data. Therefore, it allows to implement appender looking as the circular memory buffer.
I don't think that particularly String formatting brings so much overhead.
> Infinispan should enable use of log4j2
> --------------------------------------
>
> Key: ISPN-3076
> URL: https://issues.jboss.org/browse/ISPN-3076
> Project: Infinispan
> Issue Type: Enhancement
> 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
12 years
[JBoss JIRA] (ISPN-3076) Infinispan should enable use of log4j2
by Sanne Grinovero (JIRA)
[ https://issues.jboss.org/browse/ISPN-3076?page=com.atlassian.jira.plugin.... ]
Sanne Grinovero commented on ISPN-3076:
---------------------------------------
Sorry my statement had a critical typo: I meant to say
{quote}But I still don't get why Log4j*2* is of any interest to us.{quote}
In other words, I think JBoss Logging should be our default logger implementation, and we also support log4j (v1) because it's a popular choice in other containers.
Log4j V2 is not that popular yet to make this a wise move, especially until it has proven itself more efficient: I don't think we have data to back this up, for sure it defeats the purpose of even considering Log4J which should be "going with the popular version".
Very interesting of course to explore alternatives, for debugging purposes for example we could have an in memory circular buffer which skips the String formatting step: just store the parameters as they are together with the log id, the buffer content could then be "rendered" in its string form at a second time when and only if needed.
> Infinispan should enable use of log4j2
> --------------------------------------
>
> Key: ISPN-3076
> URL: https://issues.jboss.org/browse/ISPN-3076
> Project: Infinispan
> Issue Type: Enhancement
> 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
12 years
[JBoss JIRA] (ISPN-3846) CNFE: java.util.RegularEnumSet on IBM JDK 1.6
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-3846?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-3846:
-----------------------------------------------
Martin Gencur <mgencur(a)redhat.com> changed the Status of [bug 1044480|https://bugzilla.redhat.com/show_bug.cgi?id=1044480] from ON_QA to VERIFIED
> CNFE: java.util.RegularEnumSet on IBM JDK 1.6
> ---------------------------------------------
>
> Key: ISPN-3846
> URL: https://issues.jboss.org/browse/ISPN-3846
> Project: Infinispan
> Issue Type: Bug
> Components: Marshalling
> Environment: IBM Java:
> java version "1.6.0"
> Java(TM) SE Runtime Environment (build pxa6460sr13ifix-20130303_02(SR13+IV37419))
> IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Linux amd64-64 jvmxa6460sr13-20130114_134867 (JIT enabled, AOT enabled)
> J9VM - 20130114_134867
> JIT - r9_20130108_31100
> GC - 20121212_AA)
> JCL - 20130303_02
> Reporter: Martin Gencur
> Assignee: Galder Zamarreño
> Priority: Critical
> Labels: 620
> Fix For: 6.0.2.Final
>
>
> I'm getting the following exception when running tests from ISPN core on IBM JDK 1.6.
> I checked that the class is not present in the JVM. However, it is present in IBM JDK 1.7
> {code}
> org.infinispan.commons.CacheConfigurationException: Unable to instantiate class java.util.RegularEnumSet
> at org.infinispan.commons.util.Util.loadClass(Util.java:85)
> at org.infinispan.marshall.exts.EnumSetExternalizer.getEnumSetClass(EnumSetExternalizer.java:87)
> at org.infinispan.marshall.exts.EnumSetExternalizer.getRegularEnumSetClass(EnumSetExternalizer.java:83)
> at org.infinispan.marshall.exts.EnumSetExternalizer.<init>(EnumSetExternalizer.java:35)
> at org.infinispan.marshall.core.ExternalizerTable.loadInternalMarshallables(ExternalizerTable.java:220)
> at org.infinispan.marshall.core.ExternalizerTable.start(ExternalizerTable.java:144)
> 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.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:183)
> at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:869)
> at org.infinispan.factories.AbstractComponentRegistry.invokeStartMethods(AbstractComponentRegistry.java:638)
> at org.infinispan.factories.AbstractComponentRegistry.registerComponentInternal(AbstractComponentRegistry.java:207)
> at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:156)
> at org.infinispan.factories.AbstractComponentRegistry.getOrCreateComponent(AbstractComponentRegistry.java:277)
> at org.infinispan.factories.ComponentRegistry.getOrCreateComponent(ComponentRegistry.java:147)
> at org.infinispan.factories.AbstractComponentRegistry.invokeInjectionMethod(AbstractComponentRegistry.java:227)
> at org.infinispan.factories.AbstractComponentRegistry.access$000(AbstractComponentRegistry.java:65)
> at org.infinispan.factories.AbstractComponentRegistry$Component.injectDependencies(AbstractComponentRegistry.java:797)
> at org.infinispan.factories.AbstractComponentRegistry.registerComponentInternal(AbstractComponentRegistry.java:201)
> at org.infinispan.factories.ComponentRegistry.registerComponentInternal(ComponentRegistry.java:187)
> at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:156)
> at org.infinispan.factories.AbstractComponentRegistry.getOrCreateComponent(AbstractComponentRegistry.java:277)
> at org.infinispan.factories.ComponentRegistry.getOrCreateComponent(ComponentRegistry.java:150)
> at org.infinispan.factories.AbstractComponentRegistry.invokeInjectionMethod(AbstractComponentRegistry.java:227)
> at org.infinispan.factories.AbstractComponentRegistry.access$000(AbstractComponentRegistry.java:65)
> at org.infinispan.factories.AbstractComponentRegistry$Component.injectDependencies(AbstractComponentRegistry.java:797)
> at org.infinispan.factories.AbstractComponentRegistry.registerComponentInternal(AbstractComponentRegistry.java:201)
> at org.infinispan.factories.ComponentRegistry.registerComponentInternal(ComponentRegistry.java:187)
> at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:156)
> at org.infinispan.factories.AbstractComponentRegistry.getOrCreateComponent(AbstractComponentRegistry.java:277)
> at org.infinispan.factories.ComponentRegistry.getOrCreateComponent(ComponentRegistry.java:150)
> at org.infinispan.factories.AbstractComponentRegistry.invokeInjectionMethod(AbstractComponentRegistry.java:227)
> at org.infinispan.factories.AbstractComponentRegistry.access$000(AbstractComponentRegistry.java:65)
> at org.infinispan.factories.AbstractComponentRegistry$Component.injectDependencies(AbstractComponentRegistry.java:797)
> at org.infinispan.factories.AbstractComponentRegistry.registerComponentInternal(AbstractComponentRegistry.java:201)
> at org.infinispan.factories.ComponentRegistry.registerComponentInternal(ComponentRegistry.java:187)
> at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:156)
> at org.infinispan.factories.AbstractComponentRegistry.getOrCreateComponent(AbstractComponentRegistry.java:277)
> at org.infinispan.factories.ComponentRegistry.getOrCreateComponent(ComponentRegistry.java:150)
> at org.infinispan.factories.AbstractComponentRegistry.invokeInjectionMethod(AbstractComponentRegistry.java:227)
> at org.infinispan.factories.AbstractComponentRegistry.access$000(AbstractComponentRegistry.java:65)
> at org.infinispan.factories.AbstractComponentRegistry$Component.injectDependencies(AbstractComponentRegistry.java:797)
> at org.infinispan.factories.AbstractComponentRegistry.registerComponentInternal(AbstractComponentRegistry.java:201)
> at org.infinispan.factories.ComponentRegistry.registerComponentInternal(ComponentRegistry.java:187)
> at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:156)
> at org.infinispan.factories.AbstractComponentRegistry.getOrCreateComponent(AbstractComponentRegistry.java:277)
> at org.infinispan.factories.ComponentRegistry.getOrCreateComponent(ComponentRegistry.java:150)
> at org.infinispan.factories.AbstractComponentRegistry.invokeInjectionMethod(AbstractComponentRegistry.java:227)
> at org.infinispan.factories.AbstractComponentRegistry.access$000(AbstractComponentRegistry.java:65)
> at org.infinispan.factories.AbstractComponentRegistry$Component.injectDependencies(AbstractComponentRegistry.java:797)
> at org.infinispan.factories.AbstractComponentRegistry.registerComponentInternal(AbstractComponentRegistry.java:201)
> at org.infinispan.factories.ComponentRegistry.registerComponentInternal(ComponentRegistry.java:187)
> at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:156)
> at org.infinispan.factories.AbstractComponentRegistry.getOrCreateComponent(AbstractComponentRegistry.java:277)
> at org.infinispan.factories.ComponentRegistry.getOrCreateComponent(ComponentRegistry.java:150)
> at org.infinispan.factories.AbstractComponentRegistry.invokeInjectionMethod(AbstractComponentRegistry.java:227)
> at org.infinispan.factories.AbstractComponentRegistry.access$000(AbstractComponentRegistry.java:65)
> at org.infinispan.factories.AbstractComponentRegistry$Component.injectDependencies(AbstractComponentRegistry.java:797)
> at org.infinispan.factories.AbstractComponentRegistry.registerComponentInternal(AbstractComponentRegistry.java:201)
> at org.infinispan.factories.ComponentRegistry.registerComponentInternal(ComponentRegistry.java:187)
> at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:156)
> at org.infinispan.factories.AbstractComponentRegistry.getOrCreateComponent(AbstractComponentRegistry.java:277)
> at org.infinispan.factories.ComponentRegistry.getOrCreateComponent(ComponentRegistry.java:150)
> at org.infinispan.factories.AbstractComponentRegistry.invokeInjectionMethod(AbstractComponentRegistry.java:227)
> at org.infinispan.factories.AbstractComponentRegistry.access$000(AbstractComponentRegistry.java:65)
> at org.infinispan.factories.AbstractComponentRegistry$Component.injectDependencies(AbstractComponentRegistry.java:797)
> at org.infinispan.factories.AbstractComponentRegistry.registerComponentInternal(AbstractComponentRegistry.java:201)
> at org.infinispan.factories.ComponentRegistry.registerComponentInternal(ComponentRegistry.java:187)
> at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:156)
> at org.infinispan.factories.InternalCacheFactory.bootstrap(InternalCacheFactory.java:79)
> at org.infinispan.factories.InternalCacheFactory.createAndWire(InternalCacheFactory.java:58)
> at org.infinispan.factories.InternalCacheFactory.createCache(InternalCacheFactory.java:42)
> at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:549)
> at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:516)
> at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:398)
> at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:371)
> at org.infinispan.test.SingleCacheManagerTest.setup(SingleCacheManagerTest.java:32)
> at org.infinispan.test.SingleCacheManagerTest.createBeforeMethod(SingleCacheManagerTest.java:55)
> 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.invokeConfigurationMethod(Invoker.java:564)
> at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:213)
> at org.testng.internal.Invoker.invokeMethod(Invoker.java:653)
> at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901)
> at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231)
> 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:908)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:931)
> at java.lang.Thread.run(Thread.java:738)
> Caused by: java.lang.ClassNotFoundException: java.util.RegularEnumSet
> at java.lang.Class.forName(Class.java:217)
> at org.infinispan.commons.util.Util.loadClassStrict(Util.java:122)
> at org.infinispan.commons.util.Util.loadClass(Util.java:83)
> ... 102 more
> {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
[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 updated ISPN-3870:
------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1048154
> Cannot put negative numbers via CLI
> -----------------------------------
>
> Key: ISPN-3870
> URL: https://issues.jboss.org/browse/ISPN-3870
> Project: Infinispan
> Issue Type: Bug
> Components: CLI
> Reporter: Vitalii Chepeliuk
> Assignee: Mircea Markus
>
> 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 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
[JBoss JIRA] (ISPN-3870) Cannot put negative numbers via CLI
by Vitalii Chepeliuk (JIRA)
Vitalii Chepeliuk created ISPN-3870:
---------------------------------------
Summary: Cannot put negative numbers via CLI
Key: ISPN-3870
URL: https://issues.jboss.org/browse/ISPN-3870
Project: Infinispan
Issue Type: Bug
Components: CLI
Reporter: Vitalii Chepeliuk
Assignee: Mircea Markus
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 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
[JBoss JIRA] (ISPN-3869) Cannot put key with "like" value via CLI
by Vitalii Chepeliuk (JIRA)
[ https://issues.jboss.org/browse/ISPN-3869?page=com.atlassian.jira.plugin.... ]
Vitalii Chepeliuk updated ISPN-3869:
------------------------------------
Description:
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]
was:
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
> 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
>
> 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 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
[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 updated ISPN-3869:
------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1048142
> 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
>
> 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
--
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
[JBoss JIRA] (ISPN-3869) Cannot put key with "like" value via CLI
by Vitalii Chepeliuk (JIRA)
Vitalii Chepeliuk created ISPN-3869:
---------------------------------------
Summary: 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
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
--
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