Hello! If it's thin client than you should be able to simply re-open your client when it turns bad.
Then maybe it's client that closing this connection, maybe it's network stack (inactivity, etc). It is recommended to close Thin Client when not using it, rather than let it hang around. Regards, -- Ilya Kasnacheev пн, 8 июл. 2019 г. в 19:26, siva <[email protected]>: > Hi, > Above configuration is that related to thinclient? already i am using > socketTimeout on thinclient. > > like below: > > _igniteClientConfiguration = new IgniteClientConfiguration > { > Endpoints = new string[] { endPoint }, > SocketTimeout = TimeSpan.FromSeconds(30) > } > .... > .... > > public async Task CreateOrUpdateRecordAsync(string cacheName, > ICustomCacheStore data, IKeyModel key) > { > //get client configuration > try > { > // > using (IIgniteClient client = > Ignition.StartClient(this._igniteClientConfiguration)) > { > //get cache configuraation > var cache = client.GetCache<string, > ICustomCacheStore>(cacheName); > string json = > JsonConvert.SerializeObject(key,Formatting.None); > string base64EncodedKey = > Convert.ToBase64String(Encoding.UTF8.GetBytes(json)); > await cache.PutAsync(base64EncodedKey, data); > > } > } > catch (Exception ex) > { > throw; > } > } > > with above timeout getting the same exception. > > > Actually where i need to set is that need to set on server configuration in > xml file? > I thing some where i am missing docs ...i didn't find in documentation > <https://apacheignite.readme.io/docs/network-config> property > "socketWriteTimeout". > > <bean id="grid.cfg" > class="org.apache.ignite.configuration.IgniteConfiguration"> > ... > ... > <property name="communicationSpi"> > <bean > class="org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi"> > <property name="socketWriteTimeout" value="5000" /> > </bean> > </property> > > </bean> > > > > > > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
