You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2004/10/20 16:23:43 UTC
DO NOT REPLY [Bug 31801] New: -
The method Expirer.removeManagedObject (TimeStamp) leaks
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31801>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=31801
The method Expirer.removeManagedObject (TimeStamp) leaks
Summary: The method Expirer.removeManagedObject (TimeStamp) leaks
Product: Tomcat 5
Version: 5.0.0
Platform: All
OS/Version: All
Status: NEW
Severity: Critical
Priority: Other
Component: Catalina
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: david.blavier@one2team.com
The method Expirer.removeManagedObject (TimeStamp) leaks :
"managedObjs[managedCount-1] = null;" should be added here to prevent the leak.
public void removeManagedObject( TimeStamp ts ) {
for( int i=0; i< managedCount; i++ ) {
if( ts == managedObjs[i] ) {
synchronized( managedObjs ) {
managedObjs[ i ] = managedObjs[managedCount-1];
// should be added here to prevent a leak
managedObjs[managedCount-1] = null;
managedCount--;
}
return;
}
}
}
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org