inotify leaks still an issue for Groovy Login Decorators in 6.6.2

24 views

Skip to first unread message

Igor Blanco

unread,

Nov 29, 2022, 1:52:06 AM11/29/22

to CAS Community

Hi everyone:

In our test environment with CAS 6.6.2 we are having issues due to error "User limit of inotify instances reached or too many open files".

That's not something new, it's been commented in this list at least 3 previous times, but that was a year ago and none of those threads lead to an explanation or clarification if the issue was later resolved.

In 6.6.2 we are using 3 groovy scripts for different things but the one that seems to be problematic is the one used as a login decorator.

Some previous threads in this list or in the old JASIG list seem to suggest that the problem might be here:

https://github.com/apereo/cas/blob/c7a5e554f7fb95d9d24b0979cd007c22e79b73c5/support/cas-server-support-actions-core/src/main/java/org/apereo/cas/web/flow/login/RenderLoginAction.java#L48

A new "GroovyLoginWebflowDecorator" seem to be instantiated on each rendering of the login page instead of lazy loading it and reusing it.

I'm quite new to this community but if I'm not mislead the issue tracker for the project is not open for all users, so I can not post this as a bug so, what is considered the polite way of reporting such things to developers?