Christian,

It looks like you are attempting to use a DistributedMapCacheClientService with 
a DistributedSetCacheServer. I.e., you’re using a MAP-based client with a 
SET-based server. You need to use a DistributedMapCacheServer, not a 
DistributedSetCacheServer.

Thanks
-Mark


On Jan 10, 2022, at 11:54 AM, Weiss, Christian 
<[email protected]<mailto:[email protected]>> wrote:

Hi guys,

we got a problem using DistributedMapCacheClientService with 
DistributedSetCacheServer in NiFi 1.15.1.

After setting up both services we got the following exception:

2022-01-10 16:00:15,519 ERROR [Timer-Driven Process Thread-7] 
org.apache.nifi.processors.standard.Wait 
Wait[id=4a040239-ff5d-357c-2b59-3c5417c2fae6] Failed to process session due to 
java.lang.UnsupportedOperationException: Remote cache server doesn't support 
protocol version 2; Processor Administratively Yielded for 1 sec: 
java.lang.UnsupportedOperationException: Remote cache server doesn't support 
protocol version 2
java.lang.UnsupportedOperationException: Remote cache server doesn't support 
protocol version 2
        at 
org.apache.nifi.distributed.cache.client.CacheClientRequestHandler.invoke(CacheClientRequestHandler.java:94)
        at 
org.apache.nifi.distributed.cache.client.DistributedCacheClient.invoke(DistributedCacheClient.java:69)
        at 
org.apache.nifi.distributed.cache.client.NettyDistributedMapCacheClient.fetch(NettyDistributedMapCacheClient.java:268)
        at 
org.apache.nifi.distributed.cache.client.DistributedMapCacheClientService.fetch(DistributedMapCacheClientService.java:209)
        at sun.reflect.GeneratedMethodAccessor822.invoke(Unknown Source)
       at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at 
org.apache.nifi.controller.service.StandardControllerServiceInvocationHandler.invoke(StandardControllerServiceInvocationHandler.java:254)
        at 
org.apache.nifi.controller.service.StandardControllerServiceInvocationHandler.invoke(StandardControllerServiceInvocationHandler.java:105)
        at com.sun.proxy.$Proxy403.fetch(Unknown Source)
        at 
org.apache.nifi.processors.standard.WaitNotifyProtocol.getSignal(WaitNotifyProtocol.java:251)
        at org.apache.nifi.processors.standard.Wait.onTrigger(Wait.java:420)
        at 
org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
        at 
org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1273)
        at 
org.apache.nifi.controller.tasks.ConnectableTask.invoke(ConnectableTask.java:214)
        at 
org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:103)
        at org.apache.nifi.engine.FlowEngine$2.run(FlowEngine.java:110)
        at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
        at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
        at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
        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)

Configuration:

<image001.png>
<image002.png>


Anyone else with similar problems out there?

Thanks and regards,
Christian

Das SVA Mail-System ist mit einem Mailverschluesselungs-Gateway ausgestattet. 
Wenn Sie moechten, dass an Sie gerichtete E-Mails verschluesselt werden, senden 
Sie einfach eine S/MIME-signierte E-Mail oder Ihren PGP Public Key an 
[email protected]<mailto:[email protected]>.

The SVA mail system is equipped with an email encryption gateway. If you want 
email sent to you to be encrypted please send a S/MIME signed email or your PGP 
public key to [email protected]<mailto:[email protected]>.

Reply via email to