Production_ASSAM_Session timeout issue #269
Conversation
WalkthroughThe changes update the Maven project version in the POM file, adjust JPA persistence annotations in the Changes
Sequence Diagram(s)sequenceDiagram
participant Client
participant UserEntity
participant LanguageEntity
participant JPAProvider
Client->>UserEntity: Request User data (JSON)
UserEntity->>JPAProvider: Fetch m_UserLangMappings (EAGER)
JPAProvider-->>UserEntity: Return UserLangMappings
UserEntity-->>Client: Return JSON with "pan", "dob", "doj" fields
Client->>LanguageEntity: Request Language data
LanguageEntity->>JPAProvider: Fetch m_UserLangMappings (now persistent)
JPAProvider-->>LanguageEntity: Return UserLangMappings
LanguageEntity-->>Client: Return Language data with UserLangMappings
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Poem
Note ⚡️ Unit Test Generation is now available in beta!Learn more here, or try it out under "Finishing Touches" below. 📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (3)
💤 Files with no reviewable changes (1)
🧰 Additional context used🧠 Learnings (1)src/main/java/com/iemr/common/data/users/User.java (2)Learnt from: srishtigrp78 Learnt from: Zapper9982 🔇 Additional comments (5)
✨ Finishing Touches
🧪 Generate unit tests
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
|
📋 Description
JIRA ID: AMM-1670
Please provide a summary of the change and the motivation behind it. Include relevant context and details.
✅ Type of Change
ℹ️ Additional Information
Please describe how the changes were tested, and include any relevant screenshots, logs, or other information that provides additional context.
Issue:
When the Redis session expires after 30 minutes, the system attempts to fetch the user details from the database. However, due to issues like incorrect field mappings (e.g., pan), lazy loading failures (m_UserLangMappings), and missing Redis refresh logic, the user object is not returned properly—resulting in incomplete or failed API responses.
Logs :
Fixes and Corrective Actions
1. Serialization Fixes (PAN, DOB, DOJ fields)
Issue: JSON serialization failed because field names didn’t match — e.g., "pan" in JSON vs pAN in Java class.
Fix:
Added @JsonProperty("pan"), @JsonProperty("dob"), and @JsonProperty("doj") to correctly map JSON fields during deserialization.
2. Lazy Loading Fixes (m_UserLangMappings)
Issue: @onetomany(fetch = FetchType.LAZY) mapping caused deserialization errors when Redis tried to deserialize outside an active Hibernate session:
could not initialize proxy - no Session
Fix:
Changed fetch type to EAGER to ensure complete serialization.
Refer:https://pmp.piramalswasthya.org/confluence/spaces/AMRIT/pages/96043113/AMM-1670+Production_ASSAM_Session+timeout+issue
Summary by CodeRabbit
New Features
Improvements