[JBoss JIRA] (ISPN-9056) Cache metrics per node not displayed when one of nodes is stopped
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-9056?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic updated ISPN-9056:
--------------------------------------
Security: (was: Red Hat Internal)
> Cache metrics per node not displayed when one of nodes is stopped
> -----------------------------------------------------------------
>
> Key: ISPN-9056
> URL: https://issues.jboss.org/browse/ISPN-9056
> Project: Infinispan
> Issue Type: Bug
> Components: Console
> Affects Versions: 9.2.1.Final, 9.1.7.Final
> Environment: * Mac OS X
> * Out of the box JDG setup with no customization of domain and host XML files
> Reporter: Vladimir Blagojevic
> Assignee: Vladimir Blagojevic
> Priority: Minor
>
> When trying to get the stats of any cache (default, repl, memcachedCache) via the Management Console per any available node particularly when one of the JDG nodes in deliberately shut down (system calls it DEGRADED mode),the UI throws an error saying the stats couldn't be retrieved from the node shut down.
> For example, with the out of the box configuration host.xml starts two server(server-one and server-two). When the server-two is intentionally shut down and when metrics for the distributed cache "default" is looked up for all the available nodes the following error is thrown:
> WFLYCTL0030: No resource definition is registered for address [ ("host" => "master"), ("server" => "server-two"), ("subsystem" => "datagrid-infinispan"), ("cache-container" => "clustered"), ("distributed-cache" => "default") ]
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 9 months
[JBoss JIRA] (ISPN-9023) Eviction profile for “memory” type is different from “count” type
by Dmitry Katsubo (JIRA)
[ https://issues.jboss.org/browse/ISPN-9023?page=com.atlassian.jira.plugin.... ]
Dmitry Katsubo commented on ISPN-9023:
--------------------------------------
I have attached the simple [^test.7z]. When running {{mvn test}} the output should be similar to:
{code}
12:05:32.653 [main] INFO GlobalComponentRegistry - ISPN000128: Infinispan version: Infinispan 'Bastille' 9.1.1.Final
12:05:33.102 [main] INFO ISPN_9023_Test - Finished the test with configuration file infinispan_COUNT.xml and ratio 75%.
12:05:33.198 [main] INFO ISPN_9023_Test - Finished the test with configuration file infinispan_OFFHEAP.xml and ratio 75%.
12:05:33.304 [main] INFO ISPN_9023_Test - Finished the test with configuration file infinispan_MEMORY.xml and ratio 43%.
{code}
It is expected that last test against {{MEMORY}} ends with hit ratio 75%.
> Eviction profile for “memory” type is different from “count” type
> -----------------------------------------------------------------
>
> Key: ISPN-9023
> URL: https://issues.jboss.org/browse/ISPN-9023
> Project: Infinispan
> Issue Type: Bug
> Components: Eviction
> Affects Versions: 9.1.1.Final
> Environment: * Sun JDK 8 (1.8.0_92)
> * Linux x64
> Reporter: Dmitry Katsubo
> Priority: Minor
> Attachments: test.7z
>
>
> I would like to use Infinispan as cache for image binary data (Java type {{byte[]}}). I assume that Infinispan default strategy is LIFO or similar strategy that prefers to keep most recently used/added cache entity.
> In my loadtest scenario I make four calls in the round to retrieve the same entity. It is assumed that first call never hits the cache (because each round a unique entity is requested), but following three always hit the cache. So the expected profile should look like this:
> {code}
> #1: MISS-HIT-HIT-HIT
> #2: MISS-HIT-HIT-HIT
> ...
> {code}
> It works perfectly (exactly as expected above) when I configure Infinispan with COUNT eviction type with some number of entities:
> {code}
> <local-cache name="imagesCache" statistics="true">
> <!-- lifespan="30 min" max-idle="30 min" interval="1 min" -->
> <expiration lifespan="1800000" max-idle="1800000" interval="60000" />
> <memory>
> <binary eviction="COUNT" size="500" />
> </memory>
> </local-cache>
> {code}
> Cache hit ratio based on numbers I capture in loadtest: {{(2952-738)/2952 = 0.75}} and that matches the stats I observe via JMX.
> When I change the number of entities to keep in the memory (<binary eviction="COUNT" size="100" />), hit ratio does not change (as expected).
> After that I have restarted the application with only this small change in cache configuration:
> {code}
> <memory>
> <binary eviction="MEMORY" size="1000000" />
> </memory>
> {code}
> I would expect that Infinispan performance has the same profile, however it turns out that once the given amount of memory is fully allocated, newly added entities don't evict old entities but get immediately evicted. It means that roughly after 100 entities are added, all four requests to cache result cache miss (the ratio is now 0.58 instead of 0.75):
> {code}
> #1: MISS-HIT-HIT-HIT
> #2: MISS-HIT-HIT-HIT
> ...
> #101: MISS-MISS-MISS-MISS
> ...
> {code}
> If I increase the memory, indeed hit ratio comes closer to 0.75 however I would like hit ratio to be the same irrespective the memory size (provided that memory can fit at least few entities).
> Once I configure the passivation to file, memory-based eviction policy starts to work as expected:
> {code}
> <local-cache name="imagesCache" statistics="true">
> <expiration lifespan="1800000" max-idle="1800000" interval="60000" />
> <persistence passivation="true">
> <file-store path="/var/cache/infinispan" purge="true">
> <write-behind thread-pool-size="5" />
> </file-store>
> </persistence>
> <memory>
> <binary eviction="MEMORY" size="1000000" />
> </memory>
> </local-cache>
> {code}
> but I would like to force the profile I need without passivation enabled.
> Additional information is provided [on the forum|https://stackoverflow.com/questions/48420712/eviction-for-memory-ty...].
> Bottomline: If underlying component supports different eviction "modes", please expose this setting via XML so that the user of the library can control the mode.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 9 months
[JBoss JIRA] (ISPN-9055) Gui demo fails with "Could not find or load main class org.infinispan.Version"
by Ryan Emerson (JIRA)
Ryan Emerson created ISPN-9055:
----------------------------------
Summary: Gui demo fails with "Could not find or load main class org.infinispan.Version"
Key: ISPN-9055
URL: https://issues.jboss.org/browse/ISPN-9055
Project: Infinispan
Issue Type: Bug
Components: Demos and Tutorials
Affects Versions: 9.2.1.Final
Reporter: Ryan Emerson
When trying to run the demo with `java -jar infinispan-gui-demo-9.3.0-SNAPSHOT.jar -Djgroups.bind_addr=127.0.0.1 -Djava.net.preferIPv4Stack=true` the following error occurs:
{code}
Error: Could not find or load main class org.infinispan.Version
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 9 months
[JBoss JIRA] (ISPN-9023) Eviction profile for “memory” type is different from “count” type
by Dmitry Katsubo (JIRA)
[ https://issues.jboss.org/browse/ISPN-9023?page=com.atlassian.jira.plugin.... ]
Dmitry Katsubo updated ISPN-9023:
---------------------------------
Attachment: test.7z
> Eviction profile for “memory” type is different from “count” type
> -----------------------------------------------------------------
>
> Key: ISPN-9023
> URL: https://issues.jboss.org/browse/ISPN-9023
> Project: Infinispan
> Issue Type: Bug
> Components: Eviction
> Affects Versions: 9.1.1.Final
> Environment: * Sun JDK 8 (1.8.0_92)
> * Linux x64
> Reporter: Dmitry Katsubo
> Priority: Minor
> Attachments: test.7z
>
>
> I would like to use Infinispan as cache for image binary data (Java type {{byte[]}}). I assume that Infinispan default strategy is LIFO or similar strategy that prefers to keep most recently used/added cache entity.
> In my loadtest scenario I make four calls in the round to retrieve the same entity. It is assumed that first call never hits the cache (because each round a unique entity is requested), but following three always hit the cache. So the expected profile should look like this:
> {code}
> #1: MISS-HIT-HIT-HIT
> #2: MISS-HIT-HIT-HIT
> ...
> {code}
> It works perfectly (exactly as expected above) when I configure Infinispan with COUNT eviction type with some number of entities:
> {code}
> <local-cache name="imagesCache" statistics="true">
> <!-- lifespan="30 min" max-idle="30 min" interval="1 min" -->
> <expiration lifespan="1800000" max-idle="1800000" interval="60000" />
> <memory>
> <binary eviction="COUNT" size="500" />
> </memory>
> </local-cache>
> {code}
> Cache hit ratio based on numbers I capture in loadtest: {{(2952-738)/2952 = 0.75}} and that matches the stats I observe via JMX.
> When I change the number of entities to keep in the memory (<binary eviction="COUNT" size="100" />), hit ratio does not change (as expected).
> After that I have restarted the application with only this small change in cache configuration:
> {code}
> <memory>
> <binary eviction="MEMORY" size="1000000" />
> </memory>
> {code}
> I would expect that Infinispan performance has the same profile, however it turns out that once the given amount of memory is fully allocated, newly added entities don't evict old entities but get immediately evicted. It means that roughly after 100 entities are added, all four requests to cache result cache miss (the ratio is now 0.58 instead of 0.75):
> {code}
> #1: MISS-HIT-HIT-HIT
> #2: MISS-HIT-HIT-HIT
> ...
> #101: MISS-MISS-MISS-MISS
> ...
> {code}
> If I increase the memory, indeed hit ratio comes closer to 0.75 however I would like hit ratio to be the same irrespective the memory size (provided that memory can fit at least few entities).
> Once I configure the passivation to file, memory-based eviction policy starts to work as expected:
> {code}
> <local-cache name="imagesCache" statistics="true">
> <expiration lifespan="1800000" max-idle="1800000" interval="60000" />
> <persistence passivation="true">
> <file-store path="/var/cache/infinispan" purge="true">
> <write-behind thread-pool-size="5" />
> </file-store>
> </persistence>
> <memory>
> <binary eviction="MEMORY" size="1000000" />
> </memory>
> </local-cache>
> {code}
> but I would like to force the profile I need without passivation enabled.
> Additional information is provided [on the forum|https://stackoverflow.com/questions/48420712/eviction-for-memory-ty...].
> Bottomline: If underlying component supports different eviction "modes", please expose this setting via XML so that the user of the library can control the mode.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 9 months
[JBoss JIRA] (ISPN-8691) Infinispan rejects to read cache file bigger than 2147483647 (Integer.MAX_VALUE)
by Dmitry Katsubo (JIRA)
[ https://issues.jboss.org/browse/ISPN-8691?page=com.atlassian.jira.plugin.... ]
Dmitry Katsubo commented on ISPN-8691:
--------------------------------------
The cache file can be downloaded from [here|https://cloud.mail.ru/public/JcQS/z4C3c3aBD]. If the cache filesize is relatively small (500K) I don't observe any problems, e.g. Infinispan can load it into memory during the startup. In case of corruption (e.g. hardware failure) the problem would affect smaller cache files as well, right?
The cache file is definitely created and consumed by the same version of Infinispan. It is created by Infinispan on application/cache shutdown and the cache directory {{/var/cache/infinispan}} is used by one application exclusively.
> Infinispan rejects to read cache file bigger than 2147483647 (Integer.MAX_VALUE)
> --------------------------------------------------------------------------------
>
> Key: ISPN-8691
> URL: https://issues.jboss.org/browse/ISPN-8691
> Project: Infinispan
> Issue Type: Enhancement
> Components: Loaders and Stores
> Affects Versions: 9.1.1.Final
> Reporter: Dmitry Katsubo
> Priority: Minor
>
> In my scenario the cache file size created by {{SingleFileStore}} is 3.054.196.342 bytes. When this file is tried to be loaded, it fails with the following exception:
> {code}
> Caused by: org.infinispan.persistence.spi.PersistenceException: ISPN000279: Failed to read stored entries from file. Error in file /work/search-service-layer_data/infinispan/cache_test_dk83146/markupCache.dat at offset 4
> at org.infinispan.persistence.file.SingleFileStore.rebuildIndex(SingleFileStore.java:182)
> at org.infinispan.persistence.file.SingleFileStore.start(SingleFileStore.java:127)
> ... 155 more
> {code}
> Cache file content:
> {code}
> 0000000000: 46 43 53 31 80 B1 89 47 │ 00 00 00 00 00 00 00 00 FCS1?+%G
> 0000000010: 00 00 00 00 FF FF FF FF │ FF FF FF FF 02 15 4E 06 yyyyyyyy☻§N♠
> 0000000020: 05 03 04 09 00 00 00 2F │ 6F 72 67 2E 73 70 72 69 ♣♥♦○ /org.spri
> 0000000030: 6E 67 66 72 61 6D 65 77 │ 6F 72 6B 2E 63 61 63 68 ngframework.cach
> 0000000040: 65 2E 69 6E 74 65 72 63 │ 65 70 74 6F 72 2E 53 69 e.interceptor.Si
> 0000000050: 6D 70 6C 65 4B 65 79 4C │ 0A 57 03 6B 6D 93 D8 00 mpleKeyL◙W♥km"O
> 0000000060: 00 00 02 00 00 00 08 68 │ 61 73 68 43 6F 64 65 23 ☻ ◘hashCode#
> 0000000070: 00 00 00 00 06 70 61 72 │ 61 6D 73 16 00 16 15 E6 ♠params▬ ▬§?
> {code}
> The problem is that integer value 0x80B18947 is treated as signed integer in line {{SingleFileStore:181}}, hence in expression
> {code}
> if (fe.size < KEY_POS + fe.keyLen + fe.dataLen + fe.metadataLen) {
> throw log.errorReadingFileStore(file.getPath(), filePos);
> }
> {code}
> {{fe.size}} is negative and equal to -2135848633.
> I have tried to configure the persistence storage so that it gets purged on start:
> {code}
> <persistence passivation="true">
> <file-store path="/var/cache/infinispan" purge="true">
> <write-behind thread-pool-size="5" />
> </file-store>
> </persistence>
> {code}
> however this does not help as storage is first read and then purged (see also ISPN-7186).
> It is expected that {{SingleFileStore}} either does not allow to write such big entries to the cache, or handles them correctly.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 9 months
[JBoss JIRA] (ISPN-9045) Failure to change 'protocolVersion' in RemoteStoreConfiguration
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/ISPN-9045?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated ISPN-9045:
---------------------------------
Component/s: Hot Rod
> Failure to change 'protocolVersion' in RemoteStoreConfiguration
> ---------------------------------------------------------------
>
> Key: ISPN-9045
> URL: https://issues.jboss.org/browse/ISPN-9045
> Project: Infinispan
> Issue Type: Bug
> Components: Hot Rod
> Affects Versions: 9.2.0.Final, 9.2.1.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
>
> {noformat}
> 14:51:28,266 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service org.wildfly.clustering.infinispan.cache.store.web.dist: org.jboss.msc.service.StartException in service org.wildfly.clustering.infinispan.cache.store.web.dist: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1706)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1540)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1364)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalArgumentException: No enum constant org.infinispan.client.hotrod.ProtocolVersion.2.5
> at java.lang.Enum.valueOf(Enum.java:238)
> at org.infinispan.configuration.parsing.XmlConfigHelper.valueConverter(XmlConfigHelper.java:406)
> at org.infinispan.configuration.parsing.XmlConfigHelper.setAttributes(XmlConfigHelper.java:418)
> at org.infinispan.configuration.cache.AbstractStoreConfigurationBuilder.withProperties(AbstractStoreConfigurationBuilder.java:149)
> at org.jboss.as.clustering.infinispan.subsystem.StoreBuilder.getValue(StoreBuilder.java:103)
> at org.jboss.as.clustering.infinispan.subsystem.StoreBuilder.getValue(StoreBuilder.java:54)
> at org.jboss.msc.service.ValueService.start(ValueService.java:49)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1714)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693)
> ... 6 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 9 months
[JBoss JIRA] (ISPN-9045) Failure to change 'protocolVersion' in RemoteStoreConfiguration
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/ISPN-9045?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated ISPN-9045:
---------------------------------
Status: Pull Request Sent (was: Coding In Progress)
Git Pull Request: https://github.com/infinispan/infinispan/pull/5907
> Failure to change 'protocolVersion' in RemoteStoreConfiguration
> ---------------------------------------------------------------
>
> Key: ISPN-9045
> URL: https://issues.jboss.org/browse/ISPN-9045
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 9.2.0.Final, 9.2.1.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
>
> {noformat}
> 14:51:28,266 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service org.wildfly.clustering.infinispan.cache.store.web.dist: org.jboss.msc.service.StartException in service org.wildfly.clustering.infinispan.cache.store.web.dist: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1706)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1540)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1364)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalArgumentException: No enum constant org.infinispan.client.hotrod.ProtocolVersion.2.5
> at java.lang.Enum.valueOf(Enum.java:238)
> at org.infinispan.configuration.parsing.XmlConfigHelper.valueConverter(XmlConfigHelper.java:406)
> at org.infinispan.configuration.parsing.XmlConfigHelper.setAttributes(XmlConfigHelper.java:418)
> at org.infinispan.configuration.cache.AbstractStoreConfigurationBuilder.withProperties(AbstractStoreConfigurationBuilder.java:149)
> at org.jboss.as.clustering.infinispan.subsystem.StoreBuilder.getValue(StoreBuilder.java:103)
> at org.jboss.as.clustering.infinispan.subsystem.StoreBuilder.getValue(StoreBuilder.java:54)
> at org.jboss.msc.service.ValueService.start(ValueService.java:49)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1714)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693)
> ... 6 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 9 months
[JBoss JIRA] (ISPN-8719) KeySet.(iterator|spliterator|stream) not compatible with versions before 9.1
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-8719?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-8719:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> KeySet.(iterator|spliterator|stream) not compatible with versions before 9.1
> ----------------------------------------------------------------------------
>
> Key: ISPN-8719
> URL: https://issues.jboss.org/browse/ISPN-8719
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 9.1.0.Final, 9.2.0.Final
> Reporter: Marek Posolda
> Assignee: William Burns
> Priority: Critical
> Fix For: 9.1.8.Final, 9.2.2.Final, 9.3.0.Alpha1
>
> Attachments: InfinispanRemote.java
>
>
> Steps to reproduce:
> 1) Use infinispan server version 8.2.6 (or JDG server 7.1.0) and start it.
> {code}
> cd JDG_HOME/bin
> ./standalone.sh
> {code}
> 2) Create sample java project having dependency on latest dependency 9.2.0.CR1 in pom.xml:
> {code}
> <dependencies>
> <dependency>
> <groupId>org.infinispan</groupId>
> <artifactId>infinispan-core</artifactId>
> <version>9.2.0.CR1</version>
> </dependency>
> <dependency>
> <groupId>org.infinispan</groupId>
> <artifactId>infinispan-cachestore-remote</artifactId>
> <version>9.2.0.CR1</version>
> </dependency>
> </dependencies>
> {code}
> 3) Add one simple java class based on the tutorial: http://infinispan.org/tutorials/simple/remote/ . The only difference is that I use hotRod protocolVersion 2.5 and calling:
> {code}
> remoteCache.keySet().iterator().hasNext()
> {code}. I am attaching the class in attachement.
> 4) Run the class. Seeing exception in both server log and on client-side.
> Server exception
> {code}
> 10:44:20,365 ERROR [org.infinispan.server.hotrod.CacheDecodeContext] (HotRodServerWorker-6-1) ISPN005003: Exception reported: java.lang.IllegalStateException: ISPN006016: Factory 'org.infinispan.server.hotrod.HotRodServer$ToEmptyBytesKeyValueFilterConverter' not found in server
> at org.infinispan.server.hotrod.iteration.DefaultIterationManager.getFactory(DefaultIterationManager.java:148)
> at org.infinispan.server.hotrod.iteration.DefaultIterationManager.start(DefaultIterationManager.java:131)
> at org.infinispan.server.hotrod.ContextHandler.realRead(ContextHandler.java:175)
> at org.infinispan.server.hotrod.ContextHandler.lambda$channelRead0$1(ContextHandler.java:57)
> at org.infinispan.server.hotrod.ContextHandler$$Lambda$86/1492247987.run(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:144)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> Client exception:
> {code}
> Jan 24, 2018 10:44:20 AM org.infinispan.client.hotrod.impl.protocol.Codec20 checkForErrorsInResponseStatus
> WARN: ISPN004005: Error received from the server: java.lang.IllegalStateException: ISPN006016: Factory 'org.infinispan.server.hotrod.HotRodServer$ToEmptyBytesKeyValueFilterConverter' not found in server
> Exception in thread "main" org.infinispan.client.hotrod.exceptions.HotRodClientException:Request for messageId=5 returned server error (status=0x85): java.lang.IllegalStateException: ISPN006016: Factory 'org.infinispan.server.hotrod.HotRodServer$ToEmptyBytesKeyValueFilterConverter' not found in server
> at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:408)
> at org.infinispan.client.hotrod.impl.protocol.Codec20.readPartialHeader(Codec20.java:162)
> at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:148)
> at org.infinispan.client.hotrod.impl.operations.HotRodOperation.readHeaderAndValidate(HotRodOperation.java:60)
> at org.infinispan.client.hotrod.impl.operations.IterationStartOperation.executeOperation(IterationStartOperation.java:72)
> at org.infinispan.client.hotrod.impl.operations.IterationStartOperation.executeOperation(IterationStartOperation.java:21)
> at org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:56)
> at org.infinispan.client.hotrod.impl.iteration.RemoteCloseableIterator.startInternal(RemoteCloseableIterator.java:127)
> at org.infinispan.client.hotrod.impl.iteration.RemoteCloseableIterator.start(RemoteCloseableIterator.java:140)
> at org.infinispan.client.hotrod.impl.RemoteCacheImpl.retrieveEntries(RemoteCacheImpl.java:162)
> at org.infinispan.client.hotrod.impl.RemoteCacheImpl.retrieveEntries(RemoteCacheImpl.java:168)
> at org.infinispan.client.hotrod.impl.RemoteCacheImpl.retrieveEntries(RemoteCacheImpl.java:173)
> at org.infinispan.client.hotrod.impl.RemoteCacheImpl$KeySet.iterator(RemoteCacheImpl.java:553)
> at org.mposolda.ispn.InfinispanRemote.main(InfinispanRemote.java:34)
> {code}
> Indeed, When looking at this line of class RemoteCacheImpl, I see that it references the class, which seem that it was added in HotRodServer version 9. This looks like the cause of the error: https://github.com/infinispan/infinispan/blob/master/client/hotrod-client...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 9 months