[
https://issues.apache.org/jira/browse/GEODE-7254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16959515#comment-16959515
]
Alberto Gomez commented on GEODE-7254:
--------------------------------------
Hi,
According to the server logs the problem is that in one of your classes (
com.actuate.iserver.utils.cache.GeodeCacheClient), you are trying to connect to
the distributed system by invoking ClientCacheFactory.create() but there
already exists a connection to the distributed system, the one from the server.
See
[https://geode.apache.org/releases/latest/javadoc/org/apache/geode/distributed/DistributedSystem.html.|https://geode.apache.org/releases/latest/javadoc/org/apache/geode/distributed/DistributedSystem.html]
What configuration are you using to connect to the distributed system? If the
configuration used to connect to the distributed system you are using is very
similar to the one of the server then you may not encounter the problem
P.S.
See below an excerpt from the server logs with the relevant information:
"A connection to a distributed system already exists in this VM."
[severe 2019/09/30 20:47:50.576 IST iHubCacheServerProcess_100.82.204.14
<ServerConnection on port 12300 Thread 1> tid=0x53] Server connection from
[identity(100.82.204.14(5296:loner):51773:b186be82,connection=1; port=51773] :
Unexpected Error on server
java.lang.ExceptionInInitializerError
at
com.actuate.iserver.utils.CachedUserProperties.<clinit>(CachedUserProperties.java:33)
...
Caused by: java.lang.IllegalStateException: A connection to a distributed
system already exists in this VM. It has the following configuration:
ack-severe-alert-threshold="0"
ack-wait-threshold="15"
...
at
org.apache.geode.distributed.internal.InternalDistributedSystem.validateSameProperties(InternalDistributedSystem.java:2928)
at
org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:203)
at
org.apache.geode.cache.client.ClientCacheFactory.basicCreate(ClientCacheFactory.java:242)
at
org.apache.geode.cache.client.ClientCacheFactory.create(ClientCacheFactory.java:213)
at com.actuate.iserver.server.GeodeCache.getCacheInstance(GeodeCache.java:93)
at
com.actuate.iserver.server.GeodeRegion.getRegionInstance(GeodeRegion.java:21)
at
com.actuate.iserver.utils.cache.GeodeCacheClient.<clinit>(GeodeCacheClient.java:20)
... 56 more
> ServerOperationException While performing a remote put
> ------------------------------------------------------
>
> Key: GEODE-7254
> URL: https://issues.apache.org/jira/browse/GEODE-7254
> Project: Geode
> Issue Type: Bug
> Components: client/server, configuration, core
> Affects Versions: 1.8.0
> Reporter: rajesh
> Priority: Blocker
> Attachments: iHubCacheLocatorProcess.log, iHubCacheServerProcess.log,
> ihub.5296.RGOTETPF0T711Q.2019-09-30_20_44_40+0530.0.log,
> meta-iHubCacheLocatorProcess-01.log, meta-iHubCacheServerProcess-02.log
>
>
> Configuration: Locator and Server are running as different process using
> peer to peer configuration.
> while trying to insert a custom object in to a cache region using client
> cache we are getting the following exception.
> This occurs only when the Geode Locator/Server are started with log level set
> to fine, finer, finest and all.
> If the log level is set to severe, error, warning, info, config everything
> works fine.
> I am not sure if log level change has anything to do with put operation. I am
> attaching the locator and server log files.
>
> Also we have recently upgraded the geode version from 1.1.0 to 1.8. we have
> been using 1.1.0 for quite sometime without any major issues. upgraded to
> 1.8 and no code changes were made but still getting this issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
