minor readme changes

Author: mahendya1002

README.md

@@ -162,6 +162,7 @@ keytool -list -v -keystore <Your_keystore_name>`
    transaction has reached server and similar or some other exception has occurred. It is not recommended to retry on non-idempotent methods, so we are considering
    `merchantTransactionIdentifier` as idempotent key. Hence if you want to use PoolingHttpClient, merchantTransactionIdentifier field is mandatory in the payload(nvp or xml).
 
+   merchantTransactionIdentifier field should be present in the original request for all the services. The value of the merchant transaction ID must be unique for 60 days.
 
    To get more information related to connection pooling please refer wiki.
 

java/src/main/java/com/cybersource/ws/client/PoolingHttpClientConnection.java

@@ -81,9 +81,9 @@ private void initializeConnectionManager(MerchantConfig merchantConfig) throws C
                         String hostname = uri.getHost();
                         connectionManager = new PoolingHttpClientConnectionManager();
                         connectionManager.setDefaultMaxPerRoute(merchantConfig.getDefaultMaxConnectionsPerRoute());
-                        connectionManager.setDefaultSocketConfig(SocketConfig.custom().setSoKeepAlive(true).setSoTimeout(mc.getSocketTimeoutMs()).build());
+                        connectionManager.setDefaultSocketConfig(SocketConfig.custom().setSoKeepAlive(true).setSoTimeout(merchantConfig.getSocketTimeoutMs()).build());
                         connectionManager.setMaxTotal(merchantConfig.getMaxConnections());
-                        connectionManager.setValidateAfterInactivity(mc.getValidateAfterInactivityMs());
+                        connectionManager.setValidateAfterInactivity(merchantConfig.getValidateAfterInactivityMs());
                         final HttpHost httpHost = new HttpHost(hostname);
                         connectionManager.setMaxPerRoute(new HttpRoute(httpHost), merchantConfig.getMaxConnectionsPerRoute());
                         initHttpClient(merchantConfig, connectionManager);

zip/README

@@ -154,6 +154,8 @@ an I/O error/exception, when executing a request over a connection that has been
 server and similar or some other exception has occurred. It is not recommended to retry on non-idempotent methods, so we are considering `merchantTransactionIdentifier` as
 idempotent key. Hence if you want to use PoolingHttpClient, merchantTransactionIdentifier field is mandatory in the payload(nvp or xml).
 
+merchantTransactionIdentifier field should be present in the original request for all the services. The value of the merchant transaction ID must be unique for 60 days.
+
 To get more information related to connection pooling please refer wiki.
 
 ##Message Level Encryption