Production Server Time Mismatch Causing ActiveMQ Message Expiration
Supports Markdown: bold, italics, code, lists, links. Auto-saves.
No AI notes yet.
📂 Activities for this Item
Drag using ⇅ to reorder; saves automatically.
➕ Add Activity
Open Activities
Closed Activities
No closed activities.
Service Requests / Work Orders
RFS-1-13011436490
Service Request
WO-RFS-1-13011436495
Normalized time tracking
Last 30 days
Logged:
1:00
· Normalized:
1:00
2026-07-01
Day total:
1:00
Normalized (1) ·
1:00
-
Production Server Time Mismatch Causing ActiveMQ Message ExpirationLogged: 1:001:00
Time entries
1:00
-
Manual time entryRaise issue and coordinate resolution with HCO and Unite Aware team1:00 · 07:00
Meeting Notes (Project / Context)
Select a meeting to preview details.
Call with Santiago and Eladio
2026-01-20
· UA Notifications
- We discussed about the current infrastructure of Notifications. The servers in PROD are still in VMWare, but will be migrated in the next months to Proxmox.
- The current infrastructure only has the -p- servers, not the -r- ones in the diagram.
- Proxmox doesn't have a system analogous to SRM, so there is no replication or snapshot alignment.
- There will be a discussion, as HCO has to come up with a solution to have high availabilty. Otherwise the RTO/RPO will not be probably feasible
- In the ISCP all the FW rules have to be updated, they reflect old uanot servers.
iNeed Text
Defined per context on the Taxonomy page.
Templates
Attachments
No attachments yet.