IBM Data Management Community Connect with Db2, Informix, Netezza, open source, and other data experts to gain value from your data, share insights, and solve problems. Join / Log in
As the streaming analytics is going to be deprecated on May 1st, we are moving to IBM Streams on-prem. However, we met frequent timeout errors (i.e, ('Connection aborted.', OSError("(110, 'ETIMEDOUT')",)) when connecting WML, [Errno 110] Connection timed out when connecting MongoDB) on Streams on-prem, which don’t exist on the streaming analytics. I am wondering if there are some settings for Streams that I need to take care to tune my service. For example, timeout settings, connection pool management settings, network settings, etc.
To clarify your issue, you're running Streams applications on a v4.3 install and you're seeing frequent timeout errors from the application logs. Is this correct?
If so, which toolkits are you using?
Connection parameters will differ for each toolkit and you will need to check the documentation for the toolkit you're using to see if that can be configured.
It could also be an issue with the cloud services you're using.
You mentioned WML (Watson Machine Learning). If you are using the Watson Machine Learning service in IBM Cloud, double check that the endpoint you are using is for the region closest to you. See the WML documentation for a list of endpoints: https://cloud.ibm.com/apidocs/machine-learning
Since this is happening with multiple toolkits, there could also be an underlying network issue, such as a problem with the connection.
Please let us know if this helps.