Re: region name is incorrect while trying to get using region.get

[Rajesh Kumar]

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 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 of the servers
> that doesn't have the region created.
>
> The region is *REPLICATE* so the client pool "assumes" that it will be
> created in every single server, if you want a *REPLICATE* region to exist
> only in some servers you need to user server groups. The exception is
> certainly misleading, though, it shouldn't contain the name twice and it
> would probably be better to throw something like *RegionNotFoundException* 
> instead
> of *RegionDestroyedException*, but that's another discussion.
>
> Cheers.
>
> On Wed, Dec 4, 2019 at 10:32 AM Rajesh Kumar 
> wrote:
>
>> 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 connect
>> to a node where the region is not present?
>>
>> Thanks,
>> Rajesh
>>
>> On Wed, Dec 4, 2019 at 3:41 PM Ju@N  wrote:
>>
>>> 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 pointed
>>> out, I'd suggest to double check whether you have the region
>>> *AuthIdRegion* configured in all your servers.
>>> Best regards.
>>>
>>>
>>> On Wed, Dec 4, 2019 at 9:40 AM Rajesh Kumar 
>>> wrote:
>>>
 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 will take a look at the spring boot for out further releases but
 can you suggest me a fix/solution for the problem.

 Thanks,
 Rajesh


 On Wed, Dec 4, 2019 at 12:00 AM Udo Kohlmeyer  wrote:

> Reporting this, since it seems it did not make it through last night.
> On 12/3/19 12:04 AM, Udo Kohlmeyer wrote:
>
> Hi there Rajesh,
>
> Thank you for raising this. I have seen this before and I think it has
> been tracked to it actually being a toString() issue when logging the
> exception and not that it is not finding the region.
>
> Just for interest sake, why are you using Geode 1.1.0? Did you know
> Geode 1.10 is already out and we are in the process of cutting 1.11.
>
> In addition, can you confirm that you have created a region of the
> same name on the server side?
>
> If not, please create it either in Java code (pretty much the same as
> what you are doing with the client region) OR using GFSH, connected to the
> cluster to create it.
>
> If you'd like, have a look at Spring Boot for Geode
> . I'd
> recommend it.. you won't be disappointed. It will simplify the way you 
> code
> and interact with the Geode system.
>
> --Udo
> On 12/2/19 8:04 PM, Rajesh Kumar wrote:
>
> we are using apache geode 1.1.0 version. sometimes randomly while
> trying to get details from a region we are getting exceptions. On looking
> at the logs it seems the region is appended to itself and a region not
> found exception is thrown.
>
>
>
> Caused by: org.apache.geode.cache.RegionDestroyedException: Server
> connection from
> [identity(10.43.164.241(10772:loner):62563:aebd35c5,connection=1;
> port=62563]: Region named /AuthIdRegion/AuthIdRegion was not found during
> get request
>
> at
> org.apache.geode.internal.cache.tier.sockets.BaseCommand.writeRegionDestroyedEx(BaseCommand.java:633)
>
> at
> org.apache.geode.internal.cache.tier.sockets.command.Get70.cmdExecute(Get70.java:126)
>
> at
> org.apache.geode.internal.cache.tier.sockets.BaseCommand.execute(BaseCommand.java:141)
>
> at
> org.apache.geode.internal.cache.tier.sockets.ServerConnection.doNormalMsg(ServerConnection.java:783)
>
> at
> org.apache.geode.internal.cache.tier.sockets.ServerConnection.doOneMessage(ServerConnection.java:914)
>
> at
> 

Re: region name is incorrect while trying to get using region.get

[Ju@N]

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 of the servers
that doesn't have the region created.

The region is *REPLICATE* so the client pool "assumes" that it will be
created in every single server, if you want a *REPLICATE* region to exist
only in some servers you need to user server groups. The exception is
certainly misleading, though, it shouldn't contain the name twice and it
would probably be better to throw something like
*RegionNotFoundException* instead
of *RegionDestroyedException*, but that's another discussion.

Cheers.

On Wed, Dec 4, 2019 at 10:32 AM Rajesh Kumar 
wrote:

> 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 connect
> to a node where the region is not present?
>
> Thanks,
> Rajesh
>
> On Wed, Dec 4, 2019 at 3:41 PM Ju@N  wrote:
>
>> 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 pointed
>> out, I'd suggest to double check whether you have the region
>> *AuthIdRegion* configured in all your servers.
>> Best regards.
>>
>>
>> On Wed, Dec 4, 2019 at 9:40 AM Rajesh Kumar 
>> wrote:
>>
>>> 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 will take a look at the spring boot for out further releases but
>>> can you suggest me a fix/solution for the problem.
>>>
>>> Thanks,
>>> Rajesh
>>>
>>>
>>> On Wed, Dec 4, 2019 at 12:00 AM Udo Kohlmeyer  wrote:
>>>
 Reporting this, since it seems it did not make it through last night.
 On 12/3/19 12:04 AM, Udo Kohlmeyer wrote:

 Hi there Rajesh,

 Thank you for raising this. I have seen this before and I think it has
 been tracked to it actually being a toString() issue when logging the
 exception and not that it is not finding the region.

 Just for interest sake, why are you using Geode 1.1.0? Did you know
 Geode 1.10 is already out and we are in the process of cutting 1.11.

 In addition, can you confirm that you have created a region of the same
 name on the server side?

 If not, please create it either in Java code (pretty much the same as
 what you are doing with the client region) OR using GFSH, connected to the
 cluster to create it.

 If you'd like, have a look at Spring Boot for Geode
 . I'd
 recommend it.. you won't be disappointed. It will simplify the way you code
 and interact with the Geode system.

 --Udo
 On 12/2/19 8:04 PM, Rajesh Kumar wrote:

 we are using apache geode 1.1.0 version. sometimes randomly while
 trying to get details from a region we are getting exceptions. On looking
 at the logs it seems the region is appended to itself and a region not
 found exception is thrown.



 Caused by: org.apache.geode.cache.RegionDestroyedException: Server
 connection from
 [identity(10.43.164.241(10772:loner):62563:aebd35c5,connection=1;
 port=62563]: Region named /AuthIdRegion/AuthIdRegion was not found during
 get request

 at
 org.apache.geode.internal.cache.tier.sockets.BaseCommand.writeRegionDestroyedEx(BaseCommand.java:633)

 at
 org.apache.geode.internal.cache.tier.sockets.command.Get70.cmdExecute(Get70.java:126)

 at
 org.apache.geode.internal.cache.tier.sockets.BaseCommand.execute(BaseCommand.java:141)

 at
 org.apache.geode.internal.cache.tier.sockets.ServerConnection.doNormalMsg(ServerConnection.java:783)

 at
 org.apache.geode.internal.cache.tier.sockets.ServerConnection.doOneMessage(ServerConnection.java:914)

 at
 org.apache.geode.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1171)

 at
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

 at
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

 at
 org.apache.geode.internal.cache.tier.sockets.AcceptorImpl$1$1.run(AcceptorImpl.java:519)

Re: region name is incorrect while trying to get using region.get

[Rajesh Kumar]

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 connect
to a node where the region is not present?

Thanks,
Rajesh

On Wed, Dec 4, 2019 at 3:41 PM Ju@N  wrote:

> 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 pointed
> out, I'd suggest to double check whether you have the region
> *AuthIdRegion* configured in all your servers.
> Best regards.
>
>
> On Wed, Dec 4, 2019 at 9:40 AM Rajesh Kumar 
> wrote:
>
>> 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 will take a look at the spring boot for out further releases but
>> can you suggest me a fix/solution for the problem.
>>
>> Thanks,
>> Rajesh
>>
>>
>> On Wed, Dec 4, 2019 at 12:00 AM Udo Kohlmeyer  wrote:
>>
>>> Reporting this, since it seems it did not make it through last night.
>>> On 12/3/19 12:04 AM, Udo Kohlmeyer wrote:
>>>
>>> Hi there Rajesh,
>>>
>>> Thank you for raising this. I have seen this before and I think it has
>>> been tracked to it actually being a toString() issue when logging the
>>> exception and not that it is not finding the region.
>>>
>>> Just for interest sake, why are you using Geode 1.1.0? Did you know
>>> Geode 1.10 is already out and we are in the process of cutting 1.11.
>>>
>>> In addition, can you confirm that you have created a region of the same
>>> name on the server side?
>>>
>>> If not, please create it either in Java code (pretty much the same as
>>> what you are doing with the client region) OR using GFSH, connected to the
>>> cluster to create it.
>>>
>>> If you'd like, have a look at Spring Boot for Geode
>>> . I'd
>>> recommend it.. you won't be disappointed. It will simplify the way you code
>>> and interact with the Geode system.
>>>
>>> --Udo
>>> On 12/2/19 8:04 PM, Rajesh Kumar wrote:
>>>
>>> we are using apache geode 1.1.0 version. sometimes randomly while trying
>>> to get details from a region we are getting exceptions. On looking at the
>>> logs it seems the region is appended to itself and a region not found
>>> exception is thrown.
>>>
>>>
>>>
>>> Caused by: org.apache.geode.cache.RegionDestroyedException: Server
>>> connection from
>>> [identity(10.43.164.241(10772:loner):62563:aebd35c5,connection=1;
>>> port=62563]: Region named /AuthIdRegion/AuthIdRegion was not found during
>>> get request
>>>
>>> at
>>> org.apache.geode.internal.cache.tier.sockets.BaseCommand.writeRegionDestroyedEx(BaseCommand.java:633)
>>>
>>> at
>>> org.apache.geode.internal.cache.tier.sockets.command.Get70.cmdExecute(Get70.java:126)
>>>
>>> at
>>> org.apache.geode.internal.cache.tier.sockets.BaseCommand.execute(BaseCommand.java:141)
>>>
>>> at
>>> org.apache.geode.internal.cache.tier.sockets.ServerConnection.doNormalMsg(ServerConnection.java:783)
>>>
>>> at
>>> org.apache.geode.internal.cache.tier.sockets.ServerConnection.doOneMessage(ServerConnection.java:914)
>>>
>>> at
>>> org.apache.geode.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1171)
>>>
>>> at
>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>>>
>>> at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>>>
>>> at
>>> org.apache.geode.internal.cache.tier.sockets.AcceptorImpl$1$1.run(AcceptorImpl.java:519)
>>>
>>> ... 1 more
>>>
>>>
>>>
>>>
>>>
>>> The name of my region is /AuthIdRegion but it tries to query using
>>> "/AuthIdRegion/AuthIdRegion"
>>>
>>>
>>>
>>> we use client region factory to create a region instance
>>>
>>> "authIdCacheRegionInstance = GeodeCache.getCacheInstance(
>>> ).createClientRegionFactory(ClientRegionShortcut.PROXY).create("AuthIdRegion");"
>>>
>>>
>>>
>>> It will be really helpful if someone can point what exactly is the issue.
>>>
>>>
>>>
>>> Thanks,
>>>
>>> Rajesh
>>>
>>>
>
> --
> Ju@N
>

Re: region name is incorrect while trying to get using region.get

[Ju@N]

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 pointed
out, I'd suggest to double check whether you have the region *AuthIdRegion*
configured in all your servers.
Best regards.


On Wed, Dec 4, 2019 at 9:40 AM Rajesh Kumar 
wrote:

> 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 will take a look at the spring boot for out further releases but
> can you suggest me a fix/solution for the problem.
>
> Thanks,
> Rajesh
>
>
> On Wed, Dec 4, 2019 at 12:00 AM Udo Kohlmeyer  wrote:
>
>> Reporting this, since it seems it did not make it through last night.
>> On 12/3/19 12:04 AM, Udo Kohlmeyer wrote:
>>
>> Hi there Rajesh,
>>
>> Thank you for raising this. I have seen this before and I think it has
>> been tracked to it actually being a toString() issue when logging the
>> exception and not that it is not finding the region.
>>
>> Just for interest sake, why are you using Geode 1.1.0? Did you know Geode
>> 1.10 is already out and we are in the process of cutting 1.11.
>>
>> In addition, can you confirm that you have created a region of the same
>> name on the server side?
>>
>> If not, please create it either in Java code (pretty much the same as
>> what you are doing with the client region) OR using GFSH, connected to the
>> cluster to create it.
>>
>> If you'd like, have a look at Spring Boot for Geode
>> . I'd
>> recommend it.. you won't be disappointed. It will simplify the way you code
>> and interact with the Geode system.
>>
>> --Udo
>> On 12/2/19 8:04 PM, Rajesh Kumar wrote:
>>
>> we are using apache geode 1.1.0 version. sometimes randomly while trying
>> to get details from a region we are getting exceptions. On looking at the
>> logs it seems the region is appended to itself and a region not found
>> exception is thrown.
>>
>>
>>
>> Caused by: org.apache.geode.cache.RegionDestroyedException: Server
>> connection from
>> [identity(10.43.164.241(10772:loner):62563:aebd35c5,connection=1;
>> port=62563]: Region named /AuthIdRegion/AuthIdRegion was not found during
>> get request
>>
>> at
>> org.apache.geode.internal.cache.tier.sockets.BaseCommand.writeRegionDestroyedEx(BaseCommand.java:633)
>>
>> at
>> org.apache.geode.internal.cache.tier.sockets.command.Get70.cmdExecute(Get70.java:126)
>>
>> at
>> org.apache.geode.internal.cache.tier.sockets.BaseCommand.execute(BaseCommand.java:141)
>>
>> at
>> org.apache.geode.internal.cache.tier.sockets.ServerConnection.doNormalMsg(ServerConnection.java:783)
>>
>> at
>> org.apache.geode.internal.cache.tier.sockets.ServerConnection.doOneMessage(ServerConnection.java:914)
>>
>> at
>> org.apache.geode.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1171)
>>
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>>
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>>
>> at
>> org.apache.geode.internal.cache.tier.sockets.AcceptorImpl$1$1.run(AcceptorImpl.java:519)
>>
>> ... 1 more
>>
>>
>>
>>
>>
>> The name of my region is /AuthIdRegion but it tries to query using
>> "/AuthIdRegion/AuthIdRegion"
>>
>>
>>
>> we use client region factory to create a region instance
>>
>> "authIdCacheRegionInstance = GeodeCache.getCacheInstance(
>> ).createClientRegionFactory(ClientRegionShortcut.PROXY).create("AuthIdRegion");"
>>
>>
>>
>> It will be really helpful if someone can point what exactly is the issue.
>>
>>
>>
>> Thanks,
>>
>> Rajesh
>>
>>

-- 
Ju@N

Re: region name is incorrect while trying to get using region.get

[Rajesh Kumar]

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
remote get
at
org.apache.geode.cache.client.internal.AbstractOp.processObjResponse(AbstractOp.java:285)
at
org.apache.geode.cache.client.internal.GetOp$GetOpImpl.processResponse(GetOp.java:144)
at
org.apache.geode.cache.client.internal.AbstractOp.attemptReadResponse(AbstractOp.java:171)
at
org.apache.geode.cache.client.internal.AbstractOp.attempt(AbstractOp.java:382)
at
org.apache.geode.cache.client.internal.ConnectionImpl.execute(ConnectionImpl.java:266)
at
org.apache.geode.cache.client.internal.pooling.PooledConnection.execute(PooledConnection.java:332)
at
org.apache.geode.cache.client.internal.OpExecutorImpl.executeWithPossibleReAuthentication(OpExecutorImpl.java:900)
at
org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:158)
at
org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:115)
at
org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:737)
at org.apache.geode.cache.client.internal.GetOp.execute(GetOp.java:92)
at
org.apache.geode.cache.client.internal.ServerRegionProxy.get(ServerRegionProxy.java:116)
at
org.apache.geode.internal.cache.LocalRegion.findObjectInSystem(LocalRegion.java:2834)
at
org.apache.geode.internal.cache.LocalRegion.nonTxnFindObject(LocalRegion.java:1485)
at
org.apache.geode.internal.cache.LocalRegionDataView.findObject(LocalRegionDataView.java:175)
at org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1369)
at org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1302)
at org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1288)
at
org.apache.geode.internal.cache.AbstractRegion.get(AbstractRegion.java:273)
at
com.actuate.iserver.utils.cache.AuthIdCacheClient.getCachedObject(AuthIdCacheClient.java:95)
at
com.actuate.iserver.utils.CachedAuthIdProperties.getCachedUserProperties(CachedAuthIdProperties.java:95)
at
com.actuate.iserver.services.util.AuthenticationUtil.verifyTokenMappingRecord(AuthenticationUtil.java:100)
at
com.actuate.iserver.services.util.AuthenticationUtil.validateAndReturnAuthId(AuthenticationUtil.java:59)
at
com.actuate.iserver.services.util.ServiceProcessor.readHeader(ServiceProcessor.java:28)
at
com.actuate.iserver.services.EncycServiceBase.readHeader(EncycServiceBase.java:197)
at
com.actuate.iserver.services.EncycServiceBase.preExecute(EncycServiceBase.java:44)
at com.actuate.iserver.services.ServiceBase.execute(ServiceBase.java:70)
at
com.actuate.iserver.services.api.idapi.actuate11.ActuateSoapBindingImpl.getVolumeProperties(ActuateSoapBindingImpl.java:226)
at
com.actuate.schemas.actuate11.wsdl.ActuateAPIMessageReceiverInOut.invokeBusinessLogic(ActuateAPIMessageReceiverInOut.java:2085)
at
com.actuate.iserver.services.api.idapi.actuate11.ActuateAPIMessageReceiver.invokeBusinessLogic(ActuateAPIMessageReceiver.java:29)
at
org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:114)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:173)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:173)
at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:144)
at
com.actuate.webserver.NimbleAxis2Servlet.doPostWrapper(NimbleAxis2Servlet.java:88)
at com.actuate.ihub.filter.LocalFilter.processRequest(LocalFilter.java:315)
at com.actuate.ihub.filter.RequestFilter.doFilter(RequestFilter.java:269)
at
com.actuate.ihub.filter.RequestFilterChain.processFilter(RequestFilterChain.java:52)
at
com.actuate.ihub.filter.RequestFilterManager.processFilters(RequestFilterManager.java:264)
at com.actuate.ihub.web.FilterServlet.doRequest(FilterServlet.java:153)
at com.actuate.ihub.web.FilterServlet.doPost(FilterServlet.java:82)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:648)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:292)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:212)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:94)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:504)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:141)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)
at
org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:620)
at

Re: region name is incorrect while trying to get using region.get

[Rajesh Kumar]

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 will take a look at the spring boot for out further releases but can
you suggest me a fix/solution for the problem.

Thanks,
Rajesh


On Wed, Dec 4, 2019 at 12:00 AM Udo Kohlmeyer  wrote:

> Reporting this, since it seems it did not make it through last night.
> On 12/3/19 12:04 AM, Udo Kohlmeyer wrote:
>
> Hi there Rajesh,
>
> Thank you for raising this. I have seen this before and I think it has
> been tracked to it actually being a toString() issue when logging the
> exception and not that it is not finding the region.
>
> Just for interest sake, why are you using Geode 1.1.0? Did you know Geode
> 1.10 is already out and we are in the process of cutting 1.11.
>
> In addition, can you confirm that you have created a region of the same
> name on the server side?
>
> If not, please create it either in Java code (pretty much the same as what
> you are doing with the client region) OR using GFSH, connected to the
> cluster to create it.
>
> If you'd like, have a look at Spring Boot for Geode
> . I'd
> recommend it.. you won't be disappointed. It will simplify the way you code
> and interact with the Geode system.
>
> --Udo
> On 12/2/19 8:04 PM, Rajesh Kumar wrote:
>
> we are using apache geode 1.1.0 version. sometimes randomly while trying
> to get details from a region we are getting exceptions. On looking at the
> logs it seems the region is appended to itself and a region not found
> exception is thrown.
>
>
>
> Caused by: org.apache.geode.cache.RegionDestroyedException: Server
> connection from
> [identity(10.43.164.241(10772:loner):62563:aebd35c5,connection=1;
> port=62563]: Region named /AuthIdRegion/AuthIdRegion was not found during
> get request
>
> at
> org.apache.geode.internal.cache.tier.sockets.BaseCommand.writeRegionDestroyedEx(BaseCommand.java:633)
>
> at
> org.apache.geode.internal.cache.tier.sockets.command.Get70.cmdExecute(Get70.java:126)
>
> at
> org.apache.geode.internal.cache.tier.sockets.BaseCommand.execute(BaseCommand.java:141)
>
> at
> org.apache.geode.internal.cache.tier.sockets.ServerConnection.doNormalMsg(ServerConnection.java:783)
>
> at
> org.apache.geode.internal.cache.tier.sockets.ServerConnection.doOneMessage(ServerConnection.java:914)
>
> at
> org.apache.geode.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1171)
>
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>
> at
> org.apache.geode.internal.cache.tier.sockets.AcceptorImpl$1$1.run(AcceptorImpl.java:519)
>
> ... 1 more
>
>
>
>
>
> The name of my region is /AuthIdRegion but it tries to query using
> "/AuthIdRegion/AuthIdRegion"
>
>
>
> we use client region factory to create a region instance
>
> "authIdCacheRegionInstance = GeodeCache.getCacheInstance(
> ).createClientRegionFactory(ClientRegionShortcut.PROXY).create("AuthIdRegion");"
>
>
>
> It will be really helpful if someone can point what exactly is the issue.
>
>
>
> Thanks,
>
> Rajesh
>
>

Re: region name is incorrect while trying to get using region.get

[Rajesh Kumar]

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. at this
point.

Thanks,
Rajesh




On Tue, Dec 3, 2019 at 11:40 PM John Blum  wrote:

> This is an old bug (which was most certainly present in Apache Geode 1.1
> since I think I remember seeing this bug all the way up through 1.3).
> Technically, IIRC, there is no Region on the server by the name indicated
> in the misleading error message, /AuthIdRegion/AuthIdRegion, it was
> simply a problem with the error message.  Off the top of my head, I cannot
> remember what ultimately caused the RegionDestroyedException in this
> case, though.
>
> Rajesh - is it possible for you to upgrade to Apache Geode 1.10, which is
> now the latest version?  You might still have an error/configuration
> problem, but at least the error message should be more insightful.  Please
> include the full stack trace and error message along with how you
> configured the Region on the server.
>
> -j
>
>
>
> On Tue, Dec 3, 2019 at 9:53 AM Dan Smith  wrote:
>
>> Huh, that's weird. Is it possible that somewhere in your code you are
>> calling createSubregion on the returned authIdCacheRegionInstance? The
>> syntax /AuthIdRegion/AuthIdRegion indicates a region named AuthIdRegion
>> with a subregion also named AuthIdRegion.
>>
>> -Dan
>>
>> On Mon, Dec 2, 2019 at 8:04 PM Rajesh Kumar 
>> wrote:
>>
>>> we are using apache geode 1.1.0 version. sometimes randomly while trying
>>> to get details from a region we are getting exceptions. On looking at the
>>> logs it seems the region is appended to itself and a region not found
>>> exception is thrown.
>>>
>>>
>>>
>>> Caused by: org.apache.geode.cache.RegionDestroyedException: Server
>>> connection from
>>> [identity(10.43.164.241(10772:loner):62563:aebd35c5,connection=1;
>>> port=62563]: Region named /AuthIdRegion/AuthIdRegion was not found during
>>> get request
>>>
>>> at
>>> org.apache.geode.internal.cache.tier.sockets.BaseCommand.writeRegionDestroyedEx(BaseCommand.java:633)
>>>
>>> at
>>> org.apache.geode.internal.cache.tier.sockets.command.Get70.cmdExecute(Get70.java:126)
>>>
>>> at
>>> org.apache.geode.internal.cache.tier.sockets.BaseCommand.execute(BaseCommand.java:141)
>>>
>>> at
>>> org.apache.geode.internal.cache.tier.sockets.ServerConnection.doNormalMsg(ServerConnection.java:783)
>>>
>>> at
>>> org.apache.geode.internal.cache.tier.sockets.ServerConnection.doOneMessage(ServerConnection.java:914)
>>>
>>> at
>>> org.apache.geode.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1171)
>>>
>>> at
>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>>>
>>> at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>>>
>>> at
>>> org.apache.geode.internal.cache.tier.sockets.AcceptorImpl$1$1.run(AcceptorImpl.java:519)
>>>
>>> ... 1 more
>>>
>>>
>>>
>>>
>>>
>>> The name of my region is /AuthIdRegion but it tries to query using
>>> "/AuthIdRegion/AuthIdRegion"
>>>
>>>
>>>
>>> we use client region factory to create a region instance
>>>
>>> "authIdCacheRegionInstance = GeodeCache.getCacheInstance(
>>> ).createClientRegionFactory(ClientRegionShortcut.PROXY).create("AuthIdRegion");"
>>>
>>>
>>>
>>> It will be really helpful if someone can point what exactly is the issue.
>>>
>>>
>>>
>>> Thanks,
>>>
>>> Rajesh
>>>
>>
>
> --
> -John
> john.blum10101 (skype)
>

Re: region name is incorrect while trying to get using region.get

[Dan Smith]

> sometimes randomly while trying to get details from a region

Rereading this - I suspect maybe *some* of your servers don't have the
region? That might explain why sometimes it works and sometimes it doesn't.

-Dan

On Tue, Dec 3, 2019 at 11:36 AM Udo Kohlmeyer  wrote:

> Try 3?
> On 12/3/19 10:30 AM, Udo Kohlmeyer wrote:
>
> Reporting this, since it seems it did not make it through last night.
> On 12/3/19 12:04 AM, Udo Kohlmeyer wrote:
>
> Hi there Rajesh,
>
> Thank you for raising this. I have seen this before and I think it has
> been tracked to it actually being a toString() issue when logging the
> exception and not that it is not finding the region.
>
> Just for interest sake, why are you using Geode 1.1.0? Did you know Geode
> 1.10 is already out and we are in the process of cutting 1.11.
>
> In addition, can you confirm that you have created a region of the same
> name on the server side?
>
> If not, please create it either in Java code (pretty much the same as what
> you are doing with the client region) OR using GFSH, connected to the
> cluster to create it.
>
> If you'd like, have a look at Spring Boot for Geode
> . I'd
> recommend it.. you won't be disappointed. It will simplify the way you code
> and interact with the Geode system.
>
> --Udo
> On 12/2/19 8:04 PM, Rajesh Kumar wrote:
>
> we are using apache geode 1.1.0 version. sometimes randomly while trying
> to get details from a region we are getting exceptions. On looking at the
> logs it seems the region is appended to itself and a region not found
> exception is thrown.
>
>
>
> Caused by: org.apache.geode.cache.RegionDestroyedException: Server
> connection from
> [identity(10.43.164.241(10772:loner):62563:aebd35c5,connection=1;
> port=62563]: Region named /AuthIdRegion/AuthIdRegion was not found during
> get request
>
> at
> org.apache.geode.internal.cache.tier.sockets.BaseCommand.writeRegionDestroyedEx(BaseCommand.java:633)
>
> at
> org.apache.geode.internal.cache.tier.sockets.command.Get70.cmdExecute(Get70.java:126)
>
> at
> org.apache.geode.internal.cache.tier.sockets.BaseCommand.execute(BaseCommand.java:141)
>
> at
> org.apache.geode.internal.cache.tier.sockets.ServerConnection.doNormalMsg(ServerConnection.java:783)
>
> at
> org.apache.geode.internal.cache.tier.sockets.ServerConnection.doOneMessage(ServerConnection.java:914)
>
> at
> org.apache.geode.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1171)
>
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>
> at
> org.apache.geode.internal.cache.tier.sockets.AcceptorImpl$1$1.run(AcceptorImpl.java:519)
>
> ... 1 more
>
>
>
>
>
> The name of my region is /AuthIdRegion but it tries to query using
> "/AuthIdRegion/AuthIdRegion"
>
>
>
> we use client region factory to create a region instance
>
> "authIdCacheRegionInstance = GeodeCache.getCacheInstance(
> ).createClientRegionFactory(ClientRegionShortcut.PROXY).create("AuthIdRegion");"
>
>
>
> It will be really helpful if someone can point what exactly is the issue.
>
>
>
> Thanks,
>
> Rajesh
>
>

Re: region name is incorrect while trying to get using region.get

[Udo Kohlmeyer]

Try 3?

On 12/3/19 10:30 AM, Udo Kohlmeyer wrote:


Reporting this, since it seems it did not make it through last night.

On 12/3/19 12:04 AM, Udo Kohlmeyer wrote:


Hi there Rajesh,

Thank you for raising this. I have seen this before and I think it 
has been tracked to it actually being a toString() issue when logging 
the exception and not that it is not finding the region.


Just for interest sake, why are you using Geode 1.1.0? Did you know 
Geode 1.10 is already out and we are in the process of cutting 1.11.


In addition, can you confirm that you have created a region of the 
same name on the server side?


If not, please create it either in Java code (pretty much the same as 
what you are doing with the client region) OR using GFSH, connected 
to the cluster to create it.


If you'd like, have a look at Spring Boot for Geode 
. I'd 
recommend it.. you won't be disappointed. It will simplify the way 
you code and interact with the Geode system.


--Udo

On 12/2/19 8:04 PM, Rajesh Kumar wrote:


we are using apache geode 1.1.0 version. sometimes randomly while 
trying to get details from a region we are getting exceptions. On 
looking at the logs it seems the region is appended to itself and a 
region not found exception is thrown.


Caused by: org.apache.geode.cache.RegionDestroyedException: Server 
connection from 
[identity(10.43.164.241(10772:loner):62563:aebd35c5,connection=1; 
port=62563]: Region named /AuthIdRegion/AuthIdRegion was not found 
during get request


at 
org.apache.geode.internal.cache.tier.sockets.BaseCommand.writeRegionDestroyedEx(BaseCommand.java:633)


at 
org.apache.geode.internal.cache.tier.sockets.command.Get70.cmdExecute(Get70.java:126)


at 
org.apache.geode.internal.cache.tier.sockets.BaseCommand.execute(BaseCommand.java:141)


at 
org.apache.geode.internal.cache.tier.sockets.ServerConnection.doNormalMsg(ServerConnection.java:783)


at 
org.apache.geode.internal.cache.tier.sockets.ServerConnection.doOneMessage(ServerConnection.java:914)


at 
org.apache.geode.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1171)


at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)


at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)


at 
org.apache.geode.internal.cache.tier.sockets.AcceptorImpl$1$1.run(AcceptorImpl.java:519)


... 1 more

The name of my region is /AuthIdRegion but it tries to query using 
"/AuthIdRegion/AuthIdRegion"


we use client region factory to create a region instance

"authIdCacheRegionInstance = GeodeCache.getCacheInstance( 
).createClientRegionFactory(ClientRegionShortcut.PROXY).create("AuthIdRegion");"


It will be really helpful if someone can point what exactly is the 
issue.


Thanks,

Rajesh

Re: region name is incorrect while trying to get using region.get

[Gang Yan]

1. as you mentioned,  you create region on client.
"we use client region factory to create a region instance

"authIdCacheRegionInstance = GeodeCache.getCacheInstance(
).createClientRegionFactory(ClientRegionShortcut.PROXY).create("AuthIdRegion");"
"

how about the server side?
 how did you create region on server side?  by xml, gfsh or java?

2. "sometimes randomly while trying to get details from a region",  it is a
little weird ,  IMO,  if just create region on client,  every time when you
try to query an OQL, will see same error.


On Tue, Dec 3, 2019 at 10:16 AM Dan Smith  wrote:

> Perhaps the AuthIdRegion is not present on the server, and that's why you
> are getting error message (with the incorrectly formatted region name, as
> John said)?
>
> -Dan
>
> On Tue, Dec 3, 2019 at 10:10 AM John Blum  wrote:
>
>> This is an old bug (which was most certainly present in Apache Geode 1.1
>> since I think I remember seeing this bug all the way up through 1.3).
>> Technically, IIRC, there is no Region on the server by the name indicated
>> in the misleading error message, /AuthIdRegion/AuthIdRegion, it was
>> simply a problem with the error message.  Off the top of my head, I cannot
>> remember what ultimately caused the RegionDestroyedException in this
>> case, though.
>>
>> Rajesh - is it possible for you to upgrade to Apache Geode 1.10, which is
>> now the latest version?  You might still have an error/configuration
>> problem, but at least the error message should be more insightful.  Please
>> include the full stack trace and error message along with how you
>> configured the Region on the server.
>>
>> -j
>>
>>
>>
>> On Tue, Dec 3, 2019 at 9:53 AM Dan Smith  wrote:
>>
>>> Huh, that's weird. Is it possible that somewhere in your code you are
>>> calling createSubregion on the returned authIdCacheRegionInstance? The
>>> syntax /AuthIdRegion/AuthIdRegion indicates a region named AuthIdRegion
>>> with a subregion also named AuthIdRegion.
>>>
>>> -Dan
>>>
>>> On Mon, Dec 2, 2019 at 8:04 PM Rajesh Kumar 
>>> wrote:
>>>
 we are using apache geode 1.1.0 version. sometimes randomly while
 trying to get details from a region we are getting exceptions. On looking
 at the logs it seems the region is appended to itself and a region not
 found exception is thrown.



 Caused by: org.apache.geode.cache.RegionDestroyedException: Server
 connection from
 [identity(10.43.164.241(10772:loner):62563:aebd35c5,connection=1;
 port=62563]: Region named /AuthIdRegion/AuthIdRegion was not found during
 get request

 at
 org.apache.geode.internal.cache.tier.sockets.BaseCommand.writeRegionDestroyedEx(BaseCommand.java:633)

 at
 org.apache.geode.internal.cache.tier.sockets.command.Get70.cmdExecute(Get70.java:126)

 at
 org.apache.geode.internal.cache.tier.sockets.BaseCommand.execute(BaseCommand.java:141)

 at
 org.apache.geode.internal.cache.tier.sockets.ServerConnection.doNormalMsg(ServerConnection.java:783)

 at
 org.apache.geode.internal.cache.tier.sockets.ServerConnection.doOneMessage(ServerConnection.java:914)

 at
 org.apache.geode.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1171)

 at
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

 at
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

 at
 org.apache.geode.internal.cache.tier.sockets.AcceptorImpl$1$1.run(AcceptorImpl.java:519)

 ... 1 more





 The name of my region is /AuthIdRegion but it tries to query using
 "/AuthIdRegion/AuthIdRegion"



 we use client region factory to create a region instance

 "authIdCacheRegionInstance = GeodeCache.getCacheInstance(
 ).createClientRegionFactory(ClientRegionShortcut.PROXY).create("AuthIdRegion");"



 It will be really helpful if someone can point what exactly is the
 issue.



 Thanks,

 Rajesh

>>>
>>
>> --
>> -John
>> john.blum10101 (skype)
>>
>

Re: region name is incorrect while trying to get using region.get

[Dan Smith]

Perhaps the AuthIdRegion is not present on the server, and that's why you
are getting error message (with the incorrectly formatted region name, as
John said)?

-Dan

On Tue, Dec 3, 2019 at 10:10 AM John Blum  wrote:

> This is an old bug (which was most certainly present in Apache Geode 1.1
> since I think I remember seeing this bug all the way up through 1.3).
> Technically, IIRC, there is no Region on the server by the name indicated
> in the misleading error message, /AuthIdRegion/AuthIdRegion, it was
> simply a problem with the error message.  Off the top of my head, I cannot
> remember what ultimately caused the RegionDestroyedException in this
> case, though.
>
> Rajesh - is it possible for you to upgrade to Apache Geode 1.10, which is
> now the latest version?  You might still have an error/configuration
> problem, but at least the error message should be more insightful.  Please
> include the full stack trace and error message along with how you
> configured the Region on the server.
>
> -j
>
>
>
> On Tue, Dec 3, 2019 at 9:53 AM Dan Smith  wrote:
>
>> Huh, that's weird. Is it possible that somewhere in your code you are
>> calling createSubregion on the returned authIdCacheRegionInstance? The
>> syntax /AuthIdRegion/AuthIdRegion indicates a region named AuthIdRegion
>> with a subregion also named AuthIdRegion.
>>
>> -Dan
>>
>> On Mon, Dec 2, 2019 at 8:04 PM Rajesh Kumar 
>> wrote:
>>
>>> we are using apache geode 1.1.0 version. sometimes randomly while trying
>>> to get details from a region we are getting exceptions. On looking at the
>>> logs it seems the region is appended to itself and a region not found
>>> exception is thrown.
>>>
>>>
>>>
>>> Caused by: org.apache.geode.cache.RegionDestroyedException: Server
>>> connection from
>>> [identity(10.43.164.241(10772:loner):62563:aebd35c5,connection=1;
>>> port=62563]: Region named /AuthIdRegion/AuthIdRegion was not found during
>>> get request
>>>
>>> at
>>> org.apache.geode.internal.cache.tier.sockets.BaseCommand.writeRegionDestroyedEx(BaseCommand.java:633)
>>>
>>> at
>>> org.apache.geode.internal.cache.tier.sockets.command.Get70.cmdExecute(Get70.java:126)
>>>
>>> at
>>> org.apache.geode.internal.cache.tier.sockets.BaseCommand.execute(BaseCommand.java:141)
>>>
>>> at
>>> org.apache.geode.internal.cache.tier.sockets.ServerConnection.doNormalMsg(ServerConnection.java:783)
>>>
>>> at
>>> org.apache.geode.internal.cache.tier.sockets.ServerConnection.doOneMessage(ServerConnection.java:914)
>>>
>>> at
>>> org.apache.geode.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1171)
>>>
>>> at
>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>>>
>>> at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>>>
>>> at
>>> org.apache.geode.internal.cache.tier.sockets.AcceptorImpl$1$1.run(AcceptorImpl.java:519)
>>>
>>> ... 1 more
>>>
>>>
>>>
>>>
>>>
>>> The name of my region is /AuthIdRegion but it tries to query using
>>> "/AuthIdRegion/AuthIdRegion"
>>>
>>>
>>>
>>> we use client region factory to create a region instance
>>>
>>> "authIdCacheRegionInstance = GeodeCache.getCacheInstance(
>>> ).createClientRegionFactory(ClientRegionShortcut.PROXY).create("AuthIdRegion");"
>>>
>>>
>>>
>>> It will be really helpful if someone can point what exactly is the issue.
>>>
>>>
>>>
>>> Thanks,
>>>
>>> Rajesh
>>>
>>
>
> --
> -John
> john.blum10101 (skype)
>

Re: region name is incorrect while trying to get using region.get

[John Blum]

This is an old bug (which was most certainly present in Apache Geode 1.1
since I think I remember seeing this bug all the way up through 1.3).
Technically, IIRC, there is no Region on the server by the name indicated
in the misleading error message, /AuthIdRegion/AuthIdRegion, it was simply
a problem with the error message.  Off the top of my head, I cannot
remember what ultimately caused the RegionDestroyedException in this case,
though.

Rajesh - is it possible for you to upgrade to Apache Geode 1.10, which is
now the latest version?  You might still have an error/configuration
problem, but at least the error message should be more insightful.  Please
include the full stack trace and error message along with how you
configured the Region on the server.

-j



On Tue, Dec 3, 2019 at 9:53 AM Dan Smith  wrote:

> Huh, that's weird. Is it possible that somewhere in your code you are
> calling createSubregion on the returned authIdCacheRegionInstance? The
> syntax /AuthIdRegion/AuthIdRegion indicates a region named AuthIdRegion
> with a subregion also named AuthIdRegion.
>
> -Dan
>
> On Mon, Dec 2, 2019 at 8:04 PM Rajesh Kumar 
> wrote:
>
>> we are using apache geode 1.1.0 version. sometimes randomly while trying
>> to get details from a region we are getting exceptions. On looking at the
>> logs it seems the region is appended to itself and a region not found
>> exception is thrown.
>>
>>
>>
>> Caused by: org.apache.geode.cache.RegionDestroyedException: Server
>> connection from
>> [identity(10.43.164.241(10772:loner):62563:aebd35c5,connection=1;
>> port=62563]: Region named /AuthIdRegion/AuthIdRegion was not found during
>> get request
>>
>> at
>> org.apache.geode.internal.cache.tier.sockets.BaseCommand.writeRegionDestroyedEx(BaseCommand.java:633)
>>
>> at
>> org.apache.geode.internal.cache.tier.sockets.command.Get70.cmdExecute(Get70.java:126)
>>
>> at
>> org.apache.geode.internal.cache.tier.sockets.BaseCommand.execute(BaseCommand.java:141)
>>
>> at
>> org.apache.geode.internal.cache.tier.sockets.ServerConnection.doNormalMsg(ServerConnection.java:783)
>>
>> at
>> org.apache.geode.internal.cache.tier.sockets.ServerConnection.doOneMessage(ServerConnection.java:914)
>>
>> at
>> org.apache.geode.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1171)
>>
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>>
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>>
>> at
>> org.apache.geode.internal.cache.tier.sockets.AcceptorImpl$1$1.run(AcceptorImpl.java:519)
>>
>> ... 1 more
>>
>>
>>
>>
>>
>> The name of my region is /AuthIdRegion but it tries to query using
>> "/AuthIdRegion/AuthIdRegion"
>>
>>
>>
>> we use client region factory to create a region instance
>>
>> "authIdCacheRegionInstance = GeodeCache.getCacheInstance(
>> ).createClientRegionFactory(ClientRegionShortcut.PROXY).create("AuthIdRegion");"
>>
>>
>>
>> It will be really helpful if someone can point what exactly is the issue.
>>
>>
>>
>> Thanks,
>>
>> Rajesh
>>
>

-- 
-John
john.blum10101 (skype)

Re: region name is incorrect while trying to get using region.get

[Dan Smith]

Huh, that's weird. Is it possible that somewhere in your code you are
calling createSubregion on the returned authIdCacheRegionInstance? The
syntax /AuthIdRegion/AuthIdRegion indicates a region named AuthIdRegion
with a subregion also named AuthIdRegion.

-Dan

On Mon, Dec 2, 2019 at 8:04 PM Rajesh Kumar 
wrote:

> we are using apache geode 1.1.0 version. sometimes randomly while trying
> to get details from a region we are getting exceptions. On looking at the
> logs it seems the region is appended to itself and a region not found
> exception is thrown.
>
>
>
> Caused by: org.apache.geode.cache.RegionDestroyedException: Server
> connection from
> [identity(10.43.164.241(10772:loner):62563:aebd35c5,connection=1;
> port=62563]: Region named /AuthIdRegion/AuthIdRegion was not found during
> get request
>
> at
> org.apache.geode.internal.cache.tier.sockets.BaseCommand.writeRegionDestroyedEx(BaseCommand.java:633)
>
> at
> org.apache.geode.internal.cache.tier.sockets.command.Get70.cmdExecute(Get70.java:126)
>
> at
> org.apache.geode.internal.cache.tier.sockets.BaseCommand.execute(BaseCommand.java:141)
>
> at
> org.apache.geode.internal.cache.tier.sockets.ServerConnection.doNormalMsg(ServerConnection.java:783)
>
> at
> org.apache.geode.internal.cache.tier.sockets.ServerConnection.doOneMessage(ServerConnection.java:914)
>
> at
> org.apache.geode.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1171)
>
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>
> at
> org.apache.geode.internal.cache.tier.sockets.AcceptorImpl$1$1.run(AcceptorImpl.java:519)
>
> ... 1 more
>
>
>
>
>
> The name of my region is /AuthIdRegion but it tries to query using
> "/AuthIdRegion/AuthIdRegion"
>
>
>
> we use client region factory to create a region instance
>
> "authIdCacheRegionInstance = GeodeCache.getCacheInstance(
> ).createClientRegionFactory(ClientRegionShortcut.PROXY).create("AuthIdRegion");"
>
>
>
> It will be really helpful if someone can point what exactly is the issue.
>
>
>
> Thanks,
>
> Rajesh
>