Hi Jorge,
Thanks for your reply. For now our latest tweaks seem to have helped already, we changed some timeout settings in the connections being made from apache http and updated the JVM to 1.8.0_292 just in case. If the problem returns I'll look into your suggestion. Best regards, Brian ________________________________ Van: Jorge Machado <[email protected]> Verzonden: zaterdag 5 juni 2021 10:27:42 Aan: [email protected] Onderwerp: Re: SocketTimeoutExceptions and JVM version EXTERNAL SENDER: Do not click any links or open any attachments unless you trust the sender and know the content is safe. EXPÉDITEUR EXTERNE: Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe à moins qu’ils ne proviennent d’un expéditeur fiable, ou que vous ayez l'assurance que le contenu provient d'une source sûre. Is your input configured to be http or binary ? I can recommend using socket connection instead of https. You need an extra port but it could be worth. My last client we had similar issues. Ref: https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html<https://urldefense.com/v3/__https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html__;!!AaIhyw!7u7XoO7VMNDGqP6SRR1IvIUcZWBli-CwWoI0wlaR5kOkOw1TcGRkuQS9o9aitYLIlg$> Do you see a hanging thread on the input port ? On 4. Jun 2021, at 12:48, Hesselmann, Brian <[email protected]<mailto:[email protected]>> wrote: Hi all, We've been running into some problems with keeping our Nifi stable. We're running the 'official' apache/nifi:1.13.2 docker image openjdk 1.8.0_282 on a single node without clustering. Our instance receives about 5000requests per minute and after running smoothly for 8-12 hours we start seeing a lot of SocketTimeoutExceptions. I saw mentioned before that certain JVM versions have issues with SocketTimeouts, so was curious which versions have this issue so we can try upgrading to a different one. Best, Brian
