#2732 HttpClient resource leak

Memory_Leak
pending-fixed
None
jsr48-client
1
2015-06-21
2014-05-06
No

There is a resource leak in WBEMClientCIMXML.transmitRequestWorker(). If there is a Socket exception in the call to connection.connect() it is after the HttpClient object as been allocated/acquired from the pool. But the error path for those exceptions does not release the HttpClient object back to the pool. After throwing the WBEMEception, knowledge of the HttpClient object is lost. It would appear that the catch blocks for connection.connect() need to call connection.disconnect() in order to release the HttpClient object.

Discussion

  • Dave Heller

    Dave Heller - 2014-05-16

    This seems right. There is similar code in other exception handler blocks.

     
  • Dave Heller

    Dave Heller - 2014-05-16

    Patch sent for community review. During a 2 week period any
    exploiter may comment on the patch, request changes or turn it
    down completely (with good reason). For the time being the patch is part
    of the "Experimental" branch in CVS.

     
  • Dave Heller

    Dave Heller - 2014-05-16
    • status: open --> pending
    • assigned_to: Dave Heller
     
  • Dave Heller

    Dave Heller - 2015-06-21

    The community review has completed and we received no substantial criticism. Therefore the patch has been approved and merged into the "HEAD" branch. The next release will pick it up.

     
  • Dave Heller

    Dave Heller - 2015-06-21
    • status: pending --> pending-fixed
     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks