aMule Bug Tracker - aMule
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0000537aMuleMulti Platformpublic2005-08-15 05:012005-11-22 18:02
ReporterKry 
Assigned ToKry 
PriorityimmediateSeveritymajorReproducibilityalways
StatusresolvedResolutionfixed 
PlatformOSOS Version
Product VersionSVN 
Target VersionFixed in Version 
Fixed in Revision
Operating System
Summary0000537: Sockets not deleted
DescriptionAfter time, sockets become max sockets as an straigth line and no more connections are done. Well. You know what I mean.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2005-08-15 05:01KryNew Issue
2005-08-15 05:02KryStatusnew => confirmed
2005-08-15 05:18KryNote Added: 0001232
2005-08-15 06:03KryNote Added: 0001233
2005-08-15 22:49XaignarNote Added: 0001234
2005-08-17 18:54KryNote Added: 0001236
2005-08-22 01:36KryNote Added: 0001248
2005-11-22 17:59KryStatusconfirmed => assigned
2005-11-22 17:59KryAssigned To => Kry
2005-11-22 18:02KryStatusassigned => resolved
2005-11-22 18:02KryResolutionopen => fixed
2005-11-22 18:02KryNote Added: 0001504

Notes
(0001232)
Kry   
2005-08-15 05:18   
those are non uploading non downloading. I removed the upload queued and stopped all files. There are 51 clients and 502 sockets open (or to be exact, aMule thinks so), so they're elsewhere... not being deleted.
(0001233)
Kry   
2005-08-15 06:03   
And they're not deleted on cleanup because they have a socket :)
(0001234)
Xaignar   
2005-08-15 22:49   
Could the check in CClientReqSocket::CheckTimeOut() be the cause?
if ( m_client->GetKadVersion() == 0 ) {
    return false;
}
(0001236)
Kry   
2005-08-17 18:54   
I'll take a look
(0001248)
Kry   
2005-08-22 01:36   
Ok, now I know why it happens... but I ahve to talk to John about breaking backwards compatibility.
(0001504)
Kry   
2005-11-22 18:02   
Less and less to be done before 2.1.0