[
https://issues.jboss.org/browse/MODCLUSTER-217?page=com.atlassian.jira.pl...
]
Michal Babacek closed MODCLUSTER-217.
-------------------------------------
Closing. Clean-up.
At least one of the following applies:
* the issue has been thoroughly tested as a part of one of the current releases
or
* it hasn't occurred in ~2 years
or
* it's utterly harmless
request hang with a node is stop in EC2
---------------------------------------
Key: MODCLUSTER-217
URL:
https://issues.jboss.org/browse/MODCLUSTER-217
Project: mod_cluster
Issue Type: Bug
Security Level: Public(Everyone can see)
Environment: EC2
Reporter: Jean-Frederic Clere
Assignee: Michal Babacek
Priority: Minor
Fix For: MOD_CLUSTER_1_0_10_GA_CP01, 1.1.3.Final
Once stopping the EC2 the socket is closed so the cping doesn't wait for ping but
connectiontimeout which default to nodeTimeout and/or server timeout.
That affects only the first request (per process) once the node has been cleaned.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)