[
https://issues.apache.org/jira/browse/WW-5537?focusedWorklogId=1011004&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1011004
]
ASF GitHub Bot logged work on WW-5537:
--------------------------------------
Author: ASF GitHub Bot
Created on: 23/Mar/26 18:09
Start Date: 23/Mar/26 18:09
Worklog Time Spent: 10m
Work Description: sonarqubecloud[bot] commented on PR #1632:
URL: https://github.com/apache/struts/pull/1632#issuecomment-4112706232
## [](https://sonarcloud.io/dashboard?id=apache_struts&pullRequest=1632)
**Quality Gate passed**
Issues
 [0 New
issues](https://sonarcloud.io/project/issues?id=apache_struts&pullRequest=1632&issueStatuses=OPEN,CONFIRMED&sinceLeakPeriod=true)
 [0 Accepted
issues](https://sonarcloud.io/project/issues?id=apache_struts&pullRequest=1632&issueStatuses=ACCEPTED)
Measures
 [0 Security
Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_struts&pullRequest=1632&issueStatuses=OPEN,CONFIRMED&sinceLeakPeriod=true)
 [89.3% Coverage on New
Code](https://sonarcloud.io/component_measures?id=apache_struts&pullRequest=1632&metric=new_coverage&view=list)
 [0.0% Duplication on New
Code](https://sonarcloud.io/component_measures?id=apache_struts&pullRequest=1632&metric=new_duplicated_lines_density&view=list)
[See analysis details on SonarQube
Cloud](https://sonarcloud.io/dashboard?id=apache_struts&pullRequest=1632)
Issue Time Tracking
-------------------
Worklog Id: (was: 1011004)
Time Spent: 1h (was: 50m)
> Memory Leak
> ------------
>
> Key: WW-5537
> URL: https://issues.apache.org/jira/browse/WW-5537
> Project: Struts 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 6.7.0
> Environment: JDK 17
> Tomcat 9
> Reporter: Andrea Vettori
> Assignee: Lukasz Lenart
> Priority: Major
> Fix For: 6.9.0, 7.2.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Struts is leaking memory when a WAR is hot deployed in Tomcat: for each hot
> deploy some classes remain in memory instead of being garbage collected. For
> big applications this causes OOM memory exceptions very quickly for Meatspace
> exhaustion because the entire class loader of the app is not released.
> For testing the HelloWorld app from struts-examples can be used. Deploy the
> war in tomcat as the only web app in the server. For each "reload" (from
> Tomcat manager) or simply copying the war file over the deployed one, taking
> a memory dump (with jmap) and looking at the content with a memory profiler
> (such as Eclipse MAT) shows that there is one ApplicationContext class for
> each hot deploy instead of just one.
>
> The problem is present in version 6.7.4-SNAPSHOT of Feb 28th.
>
> If the server can be restarted at each deploy the problem is obviously not a
> real problem. However if a tomcat instance contains more than one application
> being able to hot deploy a single one is very useful as it does not force all
> apps down for the server restart.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)