slyouts commented on issue #3555: NIFI-6391 Prevent excessive JMS connections URL: https://github.com/apache/nifi/pull/3555#issuecomment-511935437 Added this comment to the PR, but replying just in case (I'm uncertain of who get's PR emails): The issue involves several areas of configuration, plus having a JMS broker that continually fails on Put requests. The parameters are the GC interval for the NiFi JVM, the max number of open sockets for your OS, and a Put rate that is high enough to exceed the max number of open sockets within the GC interval. How one puts this all together is beyond me. However, I've provided a detailed explanation of the problem in the ticket and examination of the code, with the understanding that the connections are cached, reveals the existence of a resource leak. While there may be better ways to deal with the cached connections, given the API I have to work with what I've offered is my best effort to deal with the problem. Steve On Fri, Jul 12, 2019 at 7:36 PM thenatog <[email protected]> wrote: > How can I replicate the original issue to confirm this PR fixes it? > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/apache/nifi/pull/3555?email_source=notifications&email_token=AMAXDVEVWJUL2HZ2WBUOJNLP7EIQNA5CNFSM4H3WJORKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZ3DNHA#issuecomment-511063708>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AMAXDVFIN6SM7I3QXYKMF33P7EIQNANCNFSM4H3WJORA> > . >
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
