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 <jb...@pivotal.io> 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 <dsm...@pivotal.io> 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 <rajeshkumar.ii...@gmail.com>
>> 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)
>
