-
Notifications
You must be signed in to change notification settings - Fork 36
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
connections aren't closed on CAT_INVALID_USER #133
Comments
Worth noting the CAT_INVALID_USER was triggered by the fact that I didn't notice the jobs config, so as a side point, could the entries in metalnx.properties be documented please? |
jobs are now gone since #214... so perhaps this is moot? |
I believe this is still an issue with the login page. When logging in using valid credentials, the When trying to login with an invalid user, I see the agent alive with jargon.
|
ah, good find. |
I finally found what was causing the CAT_INVALID_USER to leave connections open. When I updated the following code to catch Note that prior to making this change the agent stayed open for a while but garbage collection would clean up that connection when it ran. Now it will clean it up immediately. |
Full explanation of behavior and fix. Excellent. |
…UserException is encountered
…UserException is encountered
complete - closing. |
metalnx doesn't always close failed connections immediately. Our dev irods database was effectively DOS'd by metalnx creating too many connections. A lot (possibly all) of the connections which don't get cleared up have fail with CAT_INVALID_USER, something like
note that a connection which has clearly failed is open for 4 hours, when it should have been closed immediately.
The text was updated successfully, but these errors were encountered: