Connect to encrypted Db2 may appear Hang if we have incorrect IP/Port in config file

Body

If we update configuration file for Db2 with wrong IP address or Port,i.e not the IP and Port
Key-store is configured on.We may notice Connection to Database appear as hang. We are
actually experiencing a 'connection timeout'  issue that is taking a while due to multiple
attempts to reconnect.

By default retry value set to the default 50, and each reconnect takes time based upon
network settings to report a timeout,then it will take 50x time window to go through
the attempts, during which the system will appear like it is doing nothing even though it
is working.

You can configure these number of retries using following variable

COMMUNICATION_ERROR_RETRY_TIME
        Optional. The number of times the DB2 database manager will send a request to the
        centralized key manager if the connection fails or an error is returned from the
        centralized key manager. Default value: 50.

Refer
https://www.ibm.com/support/knowledgecenter/en/SSEPGG_11.1.0/com.ibm.db2.luw.admin.sec.doc/doc/t0062025.html

You can try and  Set the retry value to a low number (e.g. 2), and attempt to replicate
the scenario they experienced issues with.

  To set the retry value, modify the kmip.cfg file to add a line:

  COMMUNICATION_ERROR_RETRY_TIME=2

This parameter controls the number of times the Db2 database manager cycles through the
list of configured master and clone centralized key managers if the connection fails or
an error is returned from all of the centralized key managers. This should result in
about 2 retry wait for the TCP/IP 110 to complete the two round trips.