[MAGNOLIA-6781] Not closing URLConnection in ProductionModeClasspathFile might lead to too many open files Created: 22/Sep/16  Updated: 09/Feb/17  Resolved: 23/Sep/16

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 5.4.9
Fix Version/s: 5.4.10, 5.5

Type: Improvement Priority: Neutral
Reporter: Philip Mundt Assignee: Aleksandr Pchelintcev
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File ProductionModeClasspathFile.java.patch    
Issue Links:
Relates
relates to MAGNOLIA-6773 YamlDefinitionProvider logs "Definiti... Closed
causality
is causing MAGNOLIA-6860 ProductionModeClasspathFile might cau... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Release notes required:
Yes
Documentation update required:
Yes
Sprint: Basel 62
Story Points: 2

 Description   

Calls to info.magnolia.resourceloader.classpath.service.impl.production.ProductionModeClasspathFile#getLastModified() currently do not close the URLConnection necessary to determine the last modification date. We should at least close the connection (see info.magnolia.resourceloader.classpath.service.impl.devmode.DevelopmentModeClasspathFile#getLastModified()) and possibly only check the date once.


Generated at Mon Feb 12 04:17:46 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.