Hi All,
Thanks for your inputs, region not getting created is the root cause of
the issue. The error message was misleading and we focused our efforts on
client side.
Thanks,
Rajesh
On Wed, Dec 4, 2019 at 4:14 PM Ju@N wrote:
> Hello Rajesh,
>
> *>> Do you think this might have caused
Hello Rajesh,
*>> Do you think this might have caused the problem? if yes was it due to
the client trying to connect to a node where the region is not present?*
Yes, that's certainly the cause of the problem: you will hit the exception
every time the client tries to execute the operation on one
Hi Ju,
I have checked the logs and I can see that out of the 5 nodes in the
cluster, the region is created only in 2 nodes and in rest of the nodes
region creation failed due to various reasons. Do you think this might
have caused the problem? if yes was it due to the client trying to
Hello Rajesh,
I've seen this issue 4 or 5 times in the past and, even though the
Exception is misleading, I certainly remember that the root cause of the
issue was always the same: the client application was trying to execute the
operation on a server that didn't have the region created. As Dan
Hi John,
Please find the full stack trace below.
[Thread 69] 2019-12-02 08:35:53.323 UTC+
com.actuate.iserver.services.ServiceBase.execute()
WARNING: org.apache.geode.cache.client.ServerOperationException: remote
server on GBRPSM020006568(10772:loner):62563:aebd35c5: While performing a
Hi Udo,
Thanks for the reply. One of our clients is facing this issue in
older version of our product where we use apache geode 1.1.0. We have
upgraded to 1.8.0 in our latest release.
The region /AuthIdRegion is created by using java code, verified it by
querying it using gfsh.
we
Hi John,
Thanks for the reply. We suspected the same. One of our clients is
facing this issue in older version of our product where we use apache geode
1.1.0. We have upgraded to 1.8.0 in our latest release. But is there any
fix/solution for this as we cannot upgrade the client environment.
