Hi Stefan,
We have a workaround for now, which seems to be to set the http.client.CleanupAfterSeconds (in the runtime settings) to a value that’s lower than the interval of your scheduled event.
In our case we do a check every minute, so we set it to roughly 58 seconds and we haven't had any issues since then.
For you a setting of 12-14 seconds might do the trick.
Mendix sent us the following in the ticket:
“How is the workaround working out for you?
We are happy to inform you that your request has been nominated for implementation in the 8.9.0 release. If all goes as expected, it will be released by the end of april. Do note that unforeseen circumstances can impact the planning.”
I’ve requested a description of what they’ll be adding to the release notes, as it is still unclear what the exact problem is and what Mendix will be fixing.
I’m sure Mendix had already sent you this workaround, but if not I hope this resolves your issue as well.
Hm, that is about the connection from Mendix runtime to the database. http://hc.apache.org/httpcomponents-client-4.5.x/httpclient/apidocs/org/apache/http/conn/ConnectionPoolTimeoutException.html
You will have to look for the connection manager. There is information about the settings in paragraph
4.2 Connection Pooling of https://docs.mendix.com/refguide/custom-settings
Hi Stefan,
Have you been able to find the cause of this? We're experiencing the same issue and have no idea where to look.
Hopefully you are a lot further in your investigation than we are ;)