[jira] [Commented] (GEODE-7254) ServerOperationException While performing a remote put
[ https://issues.apache.org/jira/browse/GEODE-7254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17206031#comment-17206031 ] pankaj kumar commented on GEODE-7254: - Hi [~klund], As recommended, I tried serialization/deserialization for our class using apache commons lang3. it is working fine. but Still we are seeing the same problem for log levels fine, finer and all. Regards, Pankaj > 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, serialization >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)
[jira] [Commented] (GEODE-7254) ServerOperationException While performing a remote put
[
https://issues.apache.org/jira/browse/GEODE-7254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17148826#comment-17148826
]
Kirk Lund commented on GEODE-7254:
--
The ServerOperationException is logged at debug/fine level which is why you
only see it at debug/fine or lower.
The complete stack is:
{noformat}
org.apache.geode.cache.client.ServerOperationException: remote server on
RGOTETPF0T711Q(5296:loner):51773:b186be82: : While performing a remote put
at
org.apache.geode.cache.client.internal.PutOp$PutOpImpl.processAck(PutOp.java:384)
at
org.apache.geode.cache.client.internal.PutOp$PutOpImpl.processResponse(PutOp.java:308)
at
org.apache.geode.cache.client.internal.PutOp$PutOpImpl.attemptReadResponse(PutOp.java:449)
at
org.apache.geode.cache.client.internal.AbstractOp.attempt(AbstractOp.java:386)
at
org.apache.geode.cache.client.internal.ConnectionImpl.execute(ConnectionImpl.java:274)
at
org.apache.geode.cache.client.internal.pooling.PooledConnection.execute(PooledConnection.java:325)
at
org.apache.geode.cache.client.internal.OpExecutorImpl.executeWithPossibleReAuthentication(OpExecutorImpl.java:892)
at
org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:171)
at
org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:128)
at
org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:758)
at org.apache.geode.cache.client.internal.PutOp.execute(PutOp.java:89)
at
org.apache.geode.cache.client.internal.ServerRegionProxy.put(ServerRegionProxy.java:152)
at
org.apache.geode.internal.cache.LocalRegion.serverPut(LocalRegion.java:3032)
at
org.apache.geode.internal.cache.LocalRegion.cacheWriteBeforePut(LocalRegion.java:3144)
at
org.apache.geode.internal.cache.ProxyRegionMap.basicPut(ProxyRegionMap.java:238)
at
org.apache.geode.internal.cache.LocalRegion.virtualPut(LocalRegion.java:5664)
at
org.apache.geode.internal.cache.LocalRegionDataView.putEntry(LocalRegionDataView.java:152)
at
org.apache.geode.internal.cache.LocalRegion.basicPut(LocalRegion.java:5090)
at
org.apache.geode.internal.cache.LocalRegion.validatedPut(LocalRegion.java:1635)
at
org.apache.geode.internal.cache.LocalRegion.put(LocalRegion.java:1622)
at
org.apache.geode.internal.cache.AbstractRegion.put(AbstractRegion.java:411)
at
com.actuate.iserver.utils.cache.GeodeCacheClient.cacheObject(GeodeCacheClient.java:41)
at
com.actuate.iserver.utils.CachedUserProperties.cache(CachedUserProperties.java:88)
at
com.actuate.iserver.services.api.LoginServiceBase.updateTokenMappings(LoginServiceBase.java:144)
at
com.actuate.iserver.services.api.LoginServiceBase.doExecute(LoginServiceBase.java:139)
at com.actuate.iserver.services.ServiceBase.execute(ServiceBase.java:72)
at
com.actuate.iserver.services.api.idapi.actuate11.ActuateSoapBindingImpl.login(ActuateSoapBindingImpl.java:29)
at
com.actuate.schemas.actuate11.wsdl.ActuateAPIMessageReceiverInOut.invokeBusinessLogic(ActuateAPIMessageReceiverInOut.java:2245)
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:331)
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:660)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:741)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at
org.apache.catalina.core.StandardWrapperValve.invoke(Standard
[jira] [Commented] (GEODE-7254) ServerOperationException While performing a remote put
[ https://issues.apache.org/jira/browse/GEODE-7254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16997005#comment-16997005 ] Anirudh Boddu commented on GEODE-7254: -- Hi [~alberto.gomez], We tried setting the log levels same for both. Still we are seeing the same problem for log levels fine, finer and all. Thanks Anirudh > 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)
[jira] [Commented] (GEODE-7254) ServerOperationException While performing a remote put
[ https://issues.apache.org/jira/browse/GEODE-7254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16993274#comment-16993274 ] Alberto Gomez commented on GEODE-7254: -- Hi Rajesh, Can you try with a configuration to connect to the distributed system with ClientCacheFactory.create() with log level equal to fine,finer to be in line with the one of the server? It might be that difference between the server configuration and the one you are using to connect with ClientCacheFactory.create() the one provoking the error. BR, Alberto > 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)
[jira] [Commented] (GEODE-7254) ServerOperationException While performing a remote put
[ https://issues.apache.org/jira/browse/GEODE-7254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16993236#comment-16993236 ] rajesh commented on GEODE-7254: --- Hi Alberto, The only concern I have is why does this exception show up only when loglevel is fine,finer. when loglevel is set to any of severe, error, warning, info, config it works fine. we feel the behavior is inconsistent for different loglevels. > 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)
[jira] [Commented] (GEODE-7254) ServerOperationException While performing a remote put
[ 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 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.(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.(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)
