[ 
https://issues.apache.org/jira/browse/GEODE-7254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sarah Abbey reopened GEODE-7254:
--------------------------------
      Assignee:     (was: Sarah Abbey)

Accidentally assigned/resolved issue

> 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
>             Fix For: 1.14.0
>
>         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)

Reply via email to