Hi All,

We are getting following exception while trying to register interest on some 
Region on client boot.


2018-02-12 19:12:22,975 INFO [Heartbeat] 
com.integrien.alive.collector.HeartbeatThread.doHeartBeat - Heartbeat failed: 
Pool unexpected IOException 
connection=SubscriptionConnectionImpl[10.194.13.202:10000:closed]). Server 
unreachable: could not connect after 1 attempts
2018-02-12 19:12:22,975 DEBUG [Heartbeat] 
com.integrien.alive.collector.HeartbeatThread.doHeartBeat - The reason was:
org.apache.geode.cache.client.ServerConnectivityException: Pool unexpected 
IOException connection=SubscriptionConnectionImpl[10.194.13.202:10000:closed]). 
Server unreachable: could not connect after 1 attempts
at 
org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:798)
at 
org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:623)
at 
org.apache.geode.cache.client.internal.OpExecutorImpl.executeOnQueuesAndReturnPrimaryResult(OpExecutorImpl.java:569)
at 
org.apache.geode.cache.client.internal.PoolImpl.executeOnQueuesAndReturnPrimaryResult(PoolImpl.java:805)
at 
org.apache.geode.cache.client.internal.RegisterInterestOp.execute(RegisterInterestOp.java:58)
at 
org.apache.geode.cache.client.internal.ServerRegionProxy.registerInterest(ServerRegionProxy.java:362)
at 
org.apache.geode.internal.cache.LocalRegion.processSingleInterest(LocalRegion.java:3917)
at 
org.apache.geode.internal.cache.LocalRegion.registerInterestRegex(LocalRegion.java:3999)
at 
org.apache.geode.internal.cache.LocalRegion.registerInterestRegex(LocalRegion.java:3982)
at 
org.apache.geode.internal.cache.LocalRegion.registerInterestRegex(LocalRegion.java:3978)
at 
com.vmware.vcops.platform.common.collector.GemfireCommunicator.registerInterest(GemfireCommunicator.java:336)
at 
com.vmware.vcops.platform.common.collector.GemfireCommunicator.heartbeat(GemfireCommunicator.java:100)
at 
com.integrien.alive.collector.HeartbeatThread.doHeartBeat(HeartbeatThread.java:77)
at com.integrien.alive.collector.HeartbeatThread.run(HeartbeatThread.java:113)
at 
com.integrien.alive.common.util.BaseThread$BaseThreadRunnable.run(BaseThread.java:176)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.io.IOException: Part length ( -1,791,928,534 ) and number of 
parts ( 1 ) inconsistent
at 
org.apache.geode.internal.cache.tier.sockets.Message.readPayloadFields(Message.java:826)
at 
org.apache.geode.internal.cache.tier.sockets.ChunkedMessage.readChunk(ChunkedMessage.java:275)
at 
org.apache.geode.internal.cache.tier.sockets.ChunkedMessage.receiveChunk(ChunkedMessage.java:227)
at 
org.apache.geode.cache.client.internal.RegisterInterestOp$RegisterInterestOpImpl.processResponse(RegisterInterestOp.java:184)
at 
org.apache.geode.cache.client.internal.AbstractOp.attemptReadResponse(AbstractOp.java:159)
at 
org.apache.geode.cache.client.internal.AbstractOp.attempt(AbstractOp.java:382)
at 
org.apache.geode.cache.client.internal.ConnectionImpl.execute(ConnectionImpl.java:266)
at 
org.apache.geode.cache.client.internal.QueueConnectionImpl.execute(QueueConnectionImpl.java:165)
at 
org.apache.geode.cache.client.internal.OpExecutorImpl.executeWithPossibleReAuthentication(OpExecutorImpl.java:900)
at 
org.apache.geode.cache.client.internal.OpExecutorImpl.executeOnQueuesAndReturnPrimaryResult(OpExecutorImpl.java:562)
... 13 more


1.    I've seen couple of tickets on Geode with similar stacktraces: 
GEODE-2517<https://issues.apache.org/jira/browse/GEODE-2517>, 
GEODE-478<https://issues.apache.org/jira/browse/GEODE-478> and they all refer 
to the fact that huge amount of data is being transferred between client and 
server. But for me it is strange what can cause large data transfer during 
generic registerInterest call from client side. Could someone have info what 
kind of response client is receiving from Server during RegisterInterest that 
is so huge?

And is there any workaround (parameter value tune) we can try to get out of 
this situation?

Thanks,
Vahram.

Reply via email to