Optimize ObjectMapper Configuration in Exception Handlers#1799
Optimize ObjectMapper Configuration in Exception Handlers#1799zealot-zew wants to merge 1 commit intomosip:masterfrom
Conversation
Signed-off-by: Harihara Vardhan <hariharavardhan1234@gmail.com>
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 16 minutes and 0 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
@coderabbitai review |
|
Only users with a collaborator, contributor, member, or owner role can interact with CodeRabbit. |
Summary
This PR fixes a performance and thread-safety issue where JavaTimeModule was being redundantly registered on a shared ObjectMapper instance during every error response generation.
Problem
In both
EmailNotificationApiExceptionHandlerandApiExceptionalHandler, thesetErrors()method was callingobjectMapper.registerModule(new JavaTimeModule()). Since the ObjectMapper is an@Autowiredsingleton:Changes
@PostConstructmethod to register the JavaTimeModule exactly once when the bean is initialized.Impact