Skip to Content
avatar image
Former Member

SAP .NET Connector 3.0 Memory Leak?

We have an integration adapter that uses .net connector to talk to SAP. Our adapter runs continuously (as a windows service) periodically connecting/disconnection to SAP. There is an apparent memory leak in .NET connector  - it seems that it never fully releases connection resources and ~100K is kept after every cycle...,

We implement our own IDestinationConfiguration, send RfcConfigurationEventArgs(DELETE) evens to disconnect and even call RfcDestinationManager.RegisterDestinationConfiguration/UnregisterDestinationConfiguration for every cycle and force the GC at the end, but still memory builds up...

We tried using different versions of the connector : patch 7, Patch 9 and the latest Patch 11 - all the same.

Has anybody experience the same thing?

As much as I dislike when the control of the connection management is taken away - I dislike even more when such important integration layer (nCo) is release without all scenario tested... so the question to SAP : did you guys ever tested the connector for continuous operation ?

Thanks,

Jon

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Jun 10, 2013 at 07:22 AM

    Hi Jon,

    we are not aware of a memory leak. Please open a message with detailed information about the use case.

    Best regards,

    Markus

    Add comment
    10|10000 characters needed characters exceeded