You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by GitBox <gi...@apache.org> on 2019/07/15 15:18:52 UTC

[GitHub] [nifi] slyouts commented on issue #3555: NIFI-6391 Prevent excessive JMS connections

slyouts commented on issue #3555: NIFI-6391 Prevent excessive JMS connections
URL: https://github.com/apache/nifi/pull/3555#issuecomment-511446002
 
 
   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.

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services