Quantcast
Channel: VMware Communities: Message List
Viewing all articles
Browse latest Browse all 214415

Gemfire client timeout

$
0
0

We are trying to access an entry in client by accessing region "UserToken" thru spring configuration.

 

<?xml version="1.0" encoding="UTF-8"?>

<beans xmlns="http://www.springframework.org/schema/beans"

  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

  xmlns:gfe="http://www.springframework.org/schema/gemfire"

  xsi:schemaLocation="http://www.springframework.org/schema/beanshttp://www.springframework.org/schema/beans/spring-beans.xsd

                        http://www.springframework.org/schema/gemfirehttp://www.springframework.org/schema/gemfire/spring-gemfire-1.1.xsd">

 

  <beans profile="gemfire">

  <!-- Gemfire configuration -->

  <gfe:client-cache id="gemfire-cache" properties-ref="gemfire-props" pdx-read-serialized="false" pool-name="locatorPool" pdx-serializer="pdxSerializer" pdx-persistent="false"/>

  <gfe:pool id="locatorPool" subscription-enabled="true" server-group="print-servers" read-timeout="3000" min-connections="25" max-connections="1000" retry-attempts="0" >

  <gfe:locator host="${gf-locator-host}" port="${gf-locator-port}"/>

  <gfe:locator host="${gf-locator-host2}" port="${gf-locator-port}"/>

  </gfe:pool>

  <gfe:client-region id="UserToken" shortcut="CACHING_PROXY_HEAP_LRU" pool-name="locatorPool">

  <gfe:eviction type="HEAP_PERCENTAGE" threshold="20" />

  </gfe:client-region>

  <bean id="pdxSerializer" class="com.gemstone.gemfire.pdx.ReflectionBasedAutoSerializer">

  <constructor-arg index="0" value="com.coupons.gemfire.domain.*, com.coupons.gemfire.function.*, com.coupons.clippr.activations.domain.*"/>

  </bean>

  </beans>   

</beans>

 

We have the "read-timeout" property set to 3 secs as seen above.

On the server side, we use a firewall to drop all requests coming from client side.

When we try to access entry in "UserToken" region on the client side, we expect it to timeout after 3 secs. However, we see that it times out after 120secs.

Question is, are we using right configuration "read-timeout" for the desired result? Is there any other solution for this problem?

 

Thanks,

Mangesh


Viewing all articles
Browse latest Browse all 214415

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>