Sure I will enable FINE level logs in client to get detailed information.
For me this happens quite frequently. Client is connected to servers via
connection pool using locators. My understanding is that, if locators are
available, client should attempt to reconnect at fixed backoff interval with
indefinite attempts or with some configured timeout. Is that true? Could we
make client to auto reconnect and try indefinitely?
<gfe:pool id="geode-pool" subscription-enabled="true" server-group="${
geode.cluster.servers.groups.xxx}" read-timeout="300000" retry-attempts="3">
<gfe:locator host="${event.geode.cluster.locators[0].host}"
port="${event.geode.cluster.locators[0].port}" />
<gfe:locator host="${event.geode.cluster.locators[1].host}"
port="${event.geode.cluster.locators[1].port}" />
</gfe:pool>
<gfe:client-cache id="client-cache" pool-name="geode-pool"
pdx-serializer-ref="pdxSerializer" properties-ref="geodeProperties" />
But I am observing that, client only makes 1 attempt and decides that “Server
is unreachable”. It may happen due to network partition event or due to
unexpected shutdown of server. I will get the detailed logs for client soon.
Thanks,
Dharam
From: Anthony Baker [mailto:[email protected]]
Sent: Wednesday, September 06, 2017 7:58 PM
To: [email protected]
Subject: Re: Server unreachable: could not connect after 1 attempts [Geode
1.1.1 / GEM-118]
Those JIRA’s are related to test fixes, not product changes.
Is this a sporadic issue, or does it occur on every connection attempt? If you
can reproduce and share DEBUG level logs from the client and server that would
allow others to review and provide help.
Thanks,
Anthony
On Sep 5, 2017, at 10:23 PM, Thacker, Dharam
<[email protected]<mailto:[email protected]>> wrote:
Hello Team,
Could someone help me on this?
Thanks,
Dharam
From: Thacker, Dharam
Sent: Wednesday, August 30, 2017 4:45 PM
To: '[email protected]<mailto:[email protected]>'
Subject: RE: Server unreachable: could not connect after 1 attempts [Geode
1.1.1 / GEM-118]
Attaching related jiras,
https://issues.apache.org/jira/browse/GEODE-351
https://issues.apache.org/jira/browse/GEODE-430
Thanks,
Dharam
From: Thacker, Dharam
Sent: Wednesday, August 30, 2017 4:41 PM
To: '[email protected]<mailto:[email protected]>'
Subject: Server unreachable: could not connect after 1 attempts [Geode 1.1.1 /
GEM-118]
Hello Team,
I see below exception in my client logs and client terminates after this. As
per my knowledge this issue was already fixed as per below link but looks it
has reoccurred,
https://discuss.pivotal.io/hc/en-us/community/posts/205797168-ResultCollector-execute-thows-exception-Pool-unexpected-IOException-connection-Pooled-Connection-to-10-27-73-202-10000-Connection-DESTROYED-Server-unreachable-could-not-connect-after-1-attempts
My Version: Apache geode 1.1.1
[warning 2017/08/28 07:38:09.089 EDT <poolTimer-poc-geode-pool-11> tid=0xa1]
Pool unexpected closed socket on server connection=Pooled Connection to
Host1XX:40404: Connection[DESTROYED]). Server unreachable: could not connect
after 1 attempts
Note: I don’t have fine level logs, but I can enable and check again when it
occurs.
Thanks,
Dharam
This message is confidential and subject to terms at:
http://www.jpmorgan.com/emaildisclaimer<http://www.jpmorgan.com/emaildisclaimer>
including on confidentiality, legal privilege, viruses and monitoring of
electronic messages. If you are not the intended recipient, please delete this
message and notify the sender immediately. Any unauthorized use is strictly
prohibited.
This message is confidential and subject to terms at:
http://www.jpmorgan.com/emaildisclaimer including on confidentiality, legal
privilege, viruses and monitoring of electronic messages. If you are not the
intended recipient, please delete this message and notify the sender
immediately. Any unauthorized use is strictly prohibited.
