Tuning the IBM Content Search Services client API connection
You can use JVM arguments to tune the IBM Content Search Services client API connection to the Content Search Services server.
Two new system JVM properties are now supported for the IBM Content Search Services client API.
- com.ibm.ecmts.client.connect.timeout.secs
- This argument allows specifying the socket connection timeout value, in seconds, to connect to
the IBM Content Search Services server. For
example:
causes the API connect method to wait up to 30 seconds before timing out and returning with an error.-Dcom.ibm.ecmts.client.connect.timeout.secs=30If a new value is not specified, the default timeout is 120 seconds. This timeout value is changed from the previous default setting of 480 seconds, or 8 minutes.
- com.ibm.ecmts.client.connect.retry.count
- This argument enables you to specify the number of retry attempts when an attempted socket
connection to a IBM Content Search Services server fails.
If a new value is not specified, the default value is 1, which means if a socket connection to a IBM Content Search Services server fails, one retry attempt is made before returning a failure. For example:
sets the retry attempts to zero, so a single attempt to connect to the IBM Content Search Services server is made. If the attempt fails, errors such as "connect timed out", "connection refused", and so on are returned.-Dcom.ibm.ecmts.client.connect.retry.count=0
One use case for using these tuning arguments is in a Content Platform Engine container deployment, where connections from the Content Platform Engine to IBM Content Search Services are most likely quick, and long connection waits unnecessary. In this use case, you set the JVM options would be set in the Content Platform Engine deployment by using the parameter for the custom JVM options, or in a file named jvm.options that you place into the /overrides directory.