diff --git a/src/warden-client/doc/CHANGELOG b/src/warden-client/doc/CHANGELOG
index d0c17ef9c2eca6444fb0be6392da39b32c0f8260..5f28a2986639850d545b7d2525b9d7363b23470a 100644
--- a/src/warden-client/doc/CHANGELOG
+++ b/src/warden-client/doc/CHANGELOG
@@ -1,5 +1,6 @@
 2012-12-?? v.2.2-beta version
 --------------------------------------------------------------------------------
+- Added support of connection timeout interval                          (#925)
 - Added new getClientInfo() function allowing the client to see         (#609)
   information regarding other involved clients
 - Enhanced handling of errors. Die() functions are removed from         (#599)
diff --git a/src/warden-client/doc/README b/src/warden-client/doc/README
index a4e1dc47d2651246f06faf27f99792bbc658169a..40b0a8062ba75160f3b9cbd1404af67496d45f22 100644
--- a/src/warden-client/doc/README
+++ b/src/warden-client/doc/README
@@ -224,6 +224,14 @@ F. Configuration
     your Warden server administrator if you need to know Warden server batch 
     limits.
 
+    Option CONNECTION_TIMEOUT was added to prevent some troubles when receiving
+    large batches of new data. Default value is 60 seconds.
+
+    CONNECTION_TIMEOUT - interval in seconds to timeout connection with Warden
+                         server. If your client timeouts, consider using higher
+                         timeout number. Also, in case of receiving clients, you
+                         can optimize the MAX_RCV_EVENTS_LIMIT value.
+
     Since Warden client 2.1 there is also possibility to log status and other
     information either to STDERR of Syslog.