January 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-8676) Non-writing functional command should not go to backup

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-8676?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-8676: ------------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5670 > Non-writing functional command should not go to backup > ------------------------------------------------------ > > Key: ISPN-8676 > URL: https://issues.jboss.org/browse/ISPN-8676 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.2.0.Beta2 > Reporter: Radim Vansa > Assignee: Radim Vansa > > When a functional read/write or write-only command results in the entry not being changed, the command should not be sent to the backup owner. > Solving this for single entry is trivial (setting {{successful = false}}), the routing logic for multi-key commands is more complex. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8651) Use functional commands for JCache operations

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-8651?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-8651: ------------------------------------ Status: Open (was: New) > Use functional commands for JCache operations > --------------------------------------------- > > Key: ISPN-8651 > URL: https://issues.jboss.org/browse/ISPN-8651 > Project: Infinispan > Issue Type: Enhancement > Reporter: Radim Vansa > Assignee: Radim Vansa > > Some JCache operations (especially the {{invoke}}) cannot be executed using single command. We should run those using functional commands if possible. > -Regarding the {{invoke}} we have to find out if the {{EntryProcessor}} is marshallable. If it is we will assume that it does not have any side-effect and can be invoked on remote node; we should let the user opt-out of this behaviour through a system property.- > JSR107 spec says that implementation may require the EntryProcessor to be serializable or marshallable in some manner. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8651) Use functional commands for JCache operations

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-8651?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-8651: ------------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5670 > Use functional commands for JCache operations > --------------------------------------------- > > Key: ISPN-8651 > URL: https://issues.jboss.org/browse/ISPN-8651 > Project: Infinispan > Issue Type: Enhancement > Reporter: Radim Vansa > Assignee: Radim Vansa > > Some JCache operations (especially the {{invoke}}) cannot be executed using single command. We should run those using functional commands if possible. > -Regarding the {{invoke}} we have to find out if the {{EntryProcessor}} is marshallable. If it is we will assume that it does not have any side-effect and can be invoked on remote node; we should let the user opt-out of this behaviour through a system property.- > JSR107 spec says that implementation may require the EntryProcessor to be serializable or marshallable in some manner. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8695) Allow remote clients to be able to supply full configs to servers when creating caches

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-8695?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-8695: ------------------------------------ Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.2.0.Final 9.2.0.CR2 Resolution: Done > Allow remote clients to be able to supply full configs to servers when creating caches > -------------------------------------------------------------------------------------- > > Key: ISPN-8695 > URL: https://issues.jboss.org/browse/ISPN-8695 > Project: Infinispan > Issue Type: Enhancement > Components: Hot Rod, Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.2.0.Final, 9.2.0.CR2 > > > The current RemoteCacheContainerAdmin API only supports creating caches by supplying a template. It should also allow passing in a full configuration using the XML configuration schema. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7596) org.infinispan.commons.marshall.NotSerializableException: java.util.stream.Collectors$CollectorImpl

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-7596?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes closed ISPN-7596. ----------------------------------- Resolution: Rejected > org.infinispan.commons.marshall.NotSerializableException: java.util.stream.Collectors$CollectorImpl > --------------------------------------------------------------------------------------------------- > > Key: ISPN-7596 > URL: https://issues.jboss.org/browse/ISPN-7596 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Gustavo Fernandes > > Triggered by this snipped present in {{HotRodSourceMigrator}}: > {code:java} > Set<byte[]> allKeys = cache.keySet(); > Set<byte[]> copy = allKeys.stream().collect(Collectors.toSet()); > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7596) org.infinispan.commons.marshall.NotSerializableException: java.util.stream.Collectors$CollectorImpl

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-7596?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes commented on ISPN-7596: ----------------------------------------- Hi, this is because the collector needs to be serializable, so to fix (in Infinispan 9.1) you should wrap the collector: {code:java} Set<byte[]> allKeys = cache.keySet(); Set<byte[]> copy = allKeys.stream().collect(CacheCollectors.serializableCollector(() -> Collectors.toSet())); {code} In Infinispan 9.2 this will improved, more details on http://blog.infinispan.org/2018/01/improving-collect-for-distributed-java... > org.infinispan.commons.marshall.NotSerializableException: java.util.stream.Collectors$CollectorImpl > --------------------------------------------------------------------------------------------------- > > Key: ISPN-7596 > URL: https://issues.jboss.org/browse/ISPN-7596 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Gustavo Fernandes > > Triggered by this snipped present in {{HotRodSourceMigrator}}: > {code:java} > Set<byte[]> allKeys = cache.keySet(); > Set<byte[]> copy = allKeys.stream().collect(Collectors.toSet()); > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7596) org.infinispan.commons.marshall.NotSerializableException: java.util.stream.Collectors$CollectorImpl

by paragBorah Borah (JIRA)

[ https://issues.jboss.org/browse/ISPN-7596?page=com.atlassian.jira.plugin.... ] paragBorah Borah commented on ISPN-7596: ---------------------------------------- Exceptions :: org.infinispan.commons.marshall.NotSerializableException: java.util.stream.Collectors$CollectorImpl ERROR 01/18 19:32:01.241 [Thread-31,EXECUTOR_POOL] c.b.t.r.t.TaskExecutionWorker Failed to build result - %s com.bmc.truesight.rest.exception.ResultBuilderException: org.infinispan.commons.marshall.NotSerializableException: java.util.stream.Collectors$CollectorImpl at com.bmc.truesight.wscommon.router.rsbuilder.AbstractRouterResultBuilder.buildResult(AbstractRouterResultBuilder.java:71) at com.bmc.truesight.rest.taskexecution.TaskExecutionWorker.run(TaskExecutionWorker.java:83) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) > org.infinispan.commons.marshall.NotSerializableException: java.util.stream.Collectors$CollectorImpl > --------------------------------------------------------------------------------------------------- > > Key: ISPN-7596 > URL: https://issues.jboss.org/browse/ISPN-7596 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Gustavo Fernandes > > Triggered by this snipped present in {{HotRodSourceMigrator}}: > {code:java} > Set<byte[]> allKeys = cache.keySet(); > Set<byte[]> copy = allKeys.stream().collect(Collectors.toSet()); > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7596) org.infinispan.commons.marshall.NotSerializableException: java.util.stream.Collectors$CollectorImpl

by paragBorah Borah (JIRA)

[ https://issues.jboss.org/browse/ISPN-7596?page=com.atlassian.jira.plugin.... ] paragBorah Borah commented on ISPN-7596: ---------------------------------------- Hi [~NadirX] we are getting the same exceptions while marshalling object in infinispan. Could you please provide ur observations. > org.infinispan.commons.marshall.NotSerializableException: java.util.stream.Collectors$CollectorImpl > --------------------------------------------------------------------------------------------------- > > Key: ISPN-7596 > URL: https://issues.jboss.org/browse/ISPN-7596 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Gustavo Fernandes > > Triggered by this snipped present in {{HotRodSourceMigrator}}: > {code:java} > Set<byte[]> allKeys = cache.keySet(); > Set<byte[]> copy = allKeys.stream().collect(Collectors.toSet()); > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8726) Implement the binary memcached protocol

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8726?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8726: ---------------------------------- Description: In order to symmetrically provide security features to all the endpoints, the memcached endpoint needs to support the binary protocol as that is the only one that allows TLS encryption and SASL authn. https://github.com/memcached/memcached/wiki/BinaryProtocolRevamped was: In order to symmetrically provide security features to all the endpoints, the memcached endpoint needs to support the binary protocol as that is the only one that allows TLS encryption and SASL authn. https://github.com/couchbase/memcached/blob/master/docs/BinaryProtocol.md > Implement the binary memcached protocol > --------------------------------------- > > Key: ISPN-8726 > URL: https://issues.jboss.org/browse/ISPN-8726 > Project: Infinispan > Issue Type: Enhancement > Components: Memcached, Server > Reporter: Tristan Tarrant > > In order to symmetrically provide security features to all the endpoints, the memcached endpoint needs to support the binary protocol as that is the only one that allows TLS encryption and SASL authn. > https://github.com/memcached/memcached/wiki/BinaryProtocolRevamped -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8726) Implement the binary memcached protocol

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8726?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8726: ---------------------------------- Description: In order to symmetrically provide security features to all the endpoints, the memcached endpoint needs to support the binary protocol as that is the only one that allows TLS encryption and SASL authn. https://github.com/couchbase/memcached/blob/master/docs/BinaryProtocol.md was:In order to symmetrically provide security features to all the endpoints, the memcached endpoint needs to support the binary protocol as that is the only one that allows TLS encryption and SASL authn. > Implement the binary memcached protocol > --------------------------------------- > > Key: ISPN-8726 > URL: https://issues.jboss.org/browse/ISPN-8726 > Project: Infinispan > Issue Type: Enhancement > Components: Memcached, Server > Reporter: Tristan Tarrant > > In order to symmetrically provide security features to all the endpoints, the memcached endpoint needs to support the binary protocol as that is the only one that allows TLS encryption and SASL authn. > https://github.com/couchbase/memcached/blob/master/docs/BinaryProtocol.md -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2018