Hide Forgot
project_key: SOA Every time a login module that uses property files to configure users and roles is used, i.e. every time a user is authorized/authenticated, the property files are reread. This can introduce a performance issue. On the other hand, changes in these files to not require server restart to take effect. It would be better to monitor the files for changes and reread them only in case they were changed.
Link: Added: This issue depends JBPAPP-5275
This was first observed in 5.1. We believe that this was not the case with 5.0. Pavel Macík is writing a new performance test for this issue.
Link: Added: This issue is a dependency of JBQA-3900
We decided Oct 19 that Len would take a look at this to evaluate if this was a valid use case. Was that done?
Investigate for 5.1.(see previous comment)
The access of the files appears to happen within the initialize method of the login module, invoked on first use of the LoginContext (usually login()) As we create a new LoginContext for each authentication this will result in the file being read on each request. This is something that we may be able to mitigate.
I have checked SOA-5.0.2 and SOA-4.3.0 CP02, both exhibit the same behaviour as 5.1. I can see these files being opened up for each authentication request.
This will not be fixed in SOA 5.1.0