Open rdenarie opened 1 month ago
tribe_20240808.zip threads dumps show 8 long running threads on this part:
at io.meeds.gamification.dao.RealizationDAO.getRealizationsByObjectIdAndObjectType(RealizationDAO.java:319) at io.meeds.gamification.storage.RealizationStorage.findRealizationsByObjectIdAndObjectType(RealizationStorage.java:66) at io.meeds.gamification.service.impl.RealizationServiceImpl.findRealizationsByObjectIdAndObjectType(RealizationServiceImpl.java:560) at io.meeds.crowdin.gamification.plugin.SuggestionApprovedTriggerPlugin.getEvents(SuggestionApprovedTriggerPlugin.java:65) at io.meeds.crowdin.gamification.services.CrowdinTriggerService.handleTrigger_aroundBody0(CrowdinTriggerService.java:104) at io.meeds.crowdin.gamification.services.CrowdinTriggerService$AjcClosure1.run(CrowdinTriggerService.java:1)
@AzmiTouil I guess it is related to something we have improved lately (Nginx conf?) or maybe something we are working on (payload optimization). Can you confirm?
Hi, Today, I had to upload translations files in crowdin. I upload all languages for file gatein-portal/web/src/main/resources/locale/portal/webui_*.properties
I select the option to approve all string. This generates a lot of event seen by crowdin connector.
Then, on eXo Tribe and on Builders, we can see a lot of logs like this : Builders :
On Tribe :
On tribe, it has some side effects : People application do not display any users, document app do not display nothing ...
It seems that the trigger uses a lot of resources of the eXo/meeds server