[JBoss JIRA] (ISPN-3869) Cannot put key with "like" value via CLI
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-3869?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant reassigned ISPN-3869:
-------------------------------------
Assignee: (was: Mircea Markus)
> 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
> 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.11#6341)
11 years, 2 months
[JBoss JIRA] (ISPN-3471) storeAsBinary makes it near-impossible to use JdbcStringBasedCacheStore with non-standard key types
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-3471?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant reassigned ISPN-3471:
-------------------------------------
Assignee: (was: Mircea Markus)
> storeAsBinary makes it near-impossible to use JdbcStringBasedCacheStore with non-standard key types
> ---------------------------------------------------------------------------------------------------
>
> Key: ISPN-3471
> URL: https://issues.jboss.org/browse/ISPN-3471
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 5.3.0.Final
> Reporter: Krzysztof Sobolewski
>
> When storeAsBinary is enabled, there is a special MarshalledValueInterceptor inserted into the interceptor chain. This interceptor wraps the keys (and values) in MarshalledValue; this wrapper is then used in all interceptors as the actual key (or value). One of the interceptors that receives this wrapper is the CacheStoreInterceptor which indiscriminately passes it on to the configured CacheStore. The cache store is then supposed to store this wrapper for later retrieval.
> This works fine for cache stores that marshal the key (or value) as-is, without concern of its actual type. But there is this one very useful cache store, the JdbcStringBasedCacheStore, which is very concerned with the actual type of the key as it wants to be able to convert it to String and from String back again to the key type. When storeAsBinary is disabled, it works as designed; but when storeAsBinary is enabled, the actual key that the cache store receives may be the MarshalledValue wrapper which causes lot of confusion - the configured Key2StringMapper is not prepared to handle MarshalledValues; and even if it is, it cannot tell reliably whether it is supposed to wrap the key reconstructed from String (if it implements TwoWayKey2StringMapper).
> NOTE: this wrapping is, though, disabled if the key type is a "known" type - most notably primitives and String. That's why it's not a problem for majority of use cases where the key type is not non-standard.
> I strongly believe that [TwoWay]Key2StringMapper should never be concerned with MarshalledValues, and that JdbcStringBasedCacheStore should take upon itself the task of wrapping and unwrapping the keys as required.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (ISPN-2445) Graceful shutdown - transfer data to other nodes
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-2445?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant reassigned ISPN-2445:
-------------------------------------
Assignee: (was: Mircea Markus)
> Graceful shutdown - transfer data to other nodes
> ------------------------------------------------
>
> Key: ISPN-2445
> URL: https://issues.jboss.org/browse/ISPN-2445
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core
> Reporter: Matej Lazar
>
> Distributed cache should provide an configuration option to block shutdown until data from shutting down node is transferred to other nodes.
> This feature is useful if Infinispan is used as persistent storage.
> Without this option, in a cloud environment, where server node is deleted on scale down event, users are forced to use external storage, if they don't want to loose data.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (ISPN-3193) Capture time budgeting information
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-3193?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant reassigned ISPN-3193:
-------------------------------------
Assignee: (was: Mircea Markus)
> Capture time budgeting information
> ----------------------------------
>
> Key: ISPN-3193
> URL: https://issues.jboss.org/browse/ISPN-3193
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core
> Affects Versions: 5.3.0.Final
> Reporter: Manik Surtani
> Priority: Minor
> Labels: diagnostics, performance
>
> Should be most recent timing for each major subsystem for each type of call. E.g.,
> PUT: 10ms (locking), 10ms (datacontainer), 20ms (RPC), 30ms (CacheStore).
> GET: 0ms (locking), 5ms (datacontainer), 0ms (RPC), 10ms (CacheStore).
> etc.
> Could be implemented as a simple ringbuffer, in a specific component (TimeBudgetMonitor?) just storing the most recent N calls and that's it. Cheap to capture, cheap to store.
> This data could then be made available via a JMX operation on TimeBudgetMonitor. This is extremely valuable for tuning and debugging perf issues.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (ISPN-2726) Sporadic NPE in KeyAffinityServiceImpl
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-2726?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant reassigned ISPN-2726:
-------------------------------------
Assignee: (was: Mircea Markus)
> Sporadic NPE in KeyAffinityServiceImpl
> --------------------------------------
>
> Key: ISPN-2726
> URL: https://issues.jboss.org/browse/ISPN-2726
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 5.2.0.CR1
> Reporter: Thomas Fromm
>
> The NPE appears not often, unfortunality with enabled TRACE logging, it never appears :-( I'll keep trying to get TRACEs.
> Exception in thread "pool-70-thread-1" java.lang.NullPointerException
> at org.infinispan.affinity.KeyAffinityServiceImpl.getAddressForKey(KeyAffinityServiceImpl.java:347)
> at org.infinispan.affinity.KeyAffinityServiceImpl.access$700(KeyAffinityServiceImpl.java:59)
> at org.infinispan.affinity.KeyAffinityServiceImpl$KeyGeneratorWorker.generateKeys(KeyAffinityServiceImpl.java:270)
> at org.infinispan.affinity.KeyAffinityServiceImpl$KeyGeneratorWorker.run(KeyAffinityServiceImpl.java:242)
> 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:722)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months