Summary
|
Alert ID
|
Product & Versions Affected
| Risk Category & Score | Explicit Requirements |
| DP-444551 |
| Data Integrity: High Risk | Occurs only when LogRollback=1 is enabled |
Issue
In InterSystems IRIS versions 2025.1.0, 2025.1.1, and 2025.2, when the LogRollback debugging feature is enabled in the CPF file, transaction rollbacks do not occur. Instead of undoing the changes, the rollback operation is silently ignored. No entries are written to messages.log or journal.log, and global values are not reverted to their prior state.
Impact
This is a silent integrity failure: the system continues to function, but with incorrect values remain in place. Applications and system operations that rely on rollback semantics—whether triggered by application code, process termination, or events such as ECP disconnect—may unknowingly operate on corrupt data. Because the issue does not raise errors or generate log messages, it can remain undetected until significant business impact occurs.
This issue affects versions 2025.1.0, 2025.1.1, and 2025.2.0 of the following products:
- InterSystems IRIS
- InterSystems IRIS for Health
- HealthShare Health Connect
Resolution
This issue has been corrected in version 2025.1.2 and 2025.3.0 of these products:
- 2025.1.2 is scheduled for availability on October 22, 2025.
- 2025.3.0 is scheduled for availability on November 19, 2025.
- In the interim, customers who require the correction prior to these releases may request an ad hoc distribution for the fix (DP-444604) through the Worldwide Response Center.
- As a mitigation, disable the LogRollback parameter. This parameter is intended only as a debugging feature and is not recommended in production systems.
For More Information
If you have questions or need assistance, please contact the InterSystems
Worldwide Response Center (WRC).