Actions
Defect #2026
closedPurging temp files fails for higher TTL
Start date:
01/29/2020
Due date:
% Done:
100%
Estimated time:
Affected versions:
Owner:
Description
Version: 9.7.11
We increased temporary files TTL to twice the default value - 28 days (idm.sec.core.attachment.tempTtl=2419200000) - and purging temp files fails with the following error:
2020-01-29 12:31:57.371 INFO 1497 --- [MessageBroker-1] e.b.i.c.m.s.i.DefaultLongPollingManager : Start scheduled clearUnUseSubscribers ... 2020-01-29 12:31:57.565 ERROR 1497 --- [MessageBroker-2] o.s.s.s.TaskUtils$LoggingErrorHandler : Unexpected error occurred in scheduled task. java.lang.ArithmeticException: integer overflow at java.lang.Math.toIntExact(Math.java:1011) at eu.bcvsolutions.idm.core.ecm.service.impl.DefaultAttachmentManager.purgeTemp(DefaultAttachmentManager.java:359)
Updated by Radek Tomiška over 4 years ago
- Category changed from Scheduler to Attachment manager
- Status changed from New to In Progress
- Target version set to 10.1.0
Updated by Radek Tomiška over 4 years ago
- Status changed from In Progress to Needs feedback
- Assignee changed from Radek Tomiška to Vít Švanda
- % Done changed from 0 to 90
I fixed long ttl usage for purging temporary files, commit:
https://github.com/bcvsolutions/CzechIdMng/commit/e10aff89ee4b0e7324b25ed1c18f8fe000971fa3
Could you provide me a feedback, please?
Updated by Vít Švanda about 4 years ago
- Status changed from Needs feedback to Resolved
- Assignee changed from Vít Švanda to Radek Tomiška
- % Done changed from 90 to 100
I did review and test. Value "2419200000" works correctly now, but beware value "999999999999999" is still too much :-).
Updated by Radek Tomiška about 4 years ago
- Status changed from Resolved to Closed
Actions