-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Max File Handles reached #24
Comments
Here is the error: |
Customer has been testing this for about 3 weeks and so far they have not had any negative issues and have not run out of file handles. Attached is the update, I just made private attributes for agent and ibmQueueManager then set them if they are null, rather than creating new on each iteration. Please let me know if I can help in any way, and hopefully this can be accepted into the repo, attached. Feel free to ping me on Slack or Teams if you want to discuss this. |
I have a customer using this plugin, and they are seeing file handles exceed their ulimit(10500) after this has been running for some time. I'm asking them to capture an lsof on the machine agent when this happens again, but i took a look to make sure that the plugin is disconnecting between runs and it is, so i thought, maybe the underlying library can't handle that and isn't releasing something on each run, so i googled a bit and found this: https://stackoverflow.com/questions/69358137/ibm-mq-how-to-handle-open-close-connections-on-long-running-services-workers
I'm going to add to this, when i get that lsof output as a comment, and i will try changing the connection to be long running as a test as well, in a local code base.
Has this issue been reported or has anyone seen something like this already?
I recommended just changing the max file handles to unlimited but they can't because of NFS issues they are also dealing within their environment.
The text was updated successfully, but these errors were encountered: