none
SAP Adapter Memory Leak RRS feed

  • Question

  • Hello All,

     

    We found a memory leak problem with a SAP adaper send port

     

    We had the situation when sending around 3000 IDOCs that have a longer than allowed value for one of its attributes.

     

    During processing the host that runs the SAP send port only continuosly increases consumed memory and finally stops processing at all the IDOCs going to it.

     

    Regards,

    Raicho

    Thursday, September 25, 2008 1:24 PM

Answers

  •  

    Hi Raicho,

     

    You are absolutely right about your statement of a good product. We (Microsoft) do consider memory leak very seriously. We can try to fix this leak issue (if it is actually Adapter issue) in our next release however if you need immediate fix, I suggest you to work with our support team (PSS) and request for a QFE. The QFE request needs to have proper business justification so that MS can evaluate the priority of the request.

     

    Thanks,

    Koushik

     

     

    Wednesday, October 29, 2008 3:55 PM

All replies

  • If you reduce the value to what is within the allowed length, does the leak go away?

    Thursday, September 25, 2008 2:31 PM
  • Yes it does.

    Adapter leaks only in the case of passing too long data in the IDOC.

    Thursday, September 25, 2008 2:33 PM
  • Thanks, we'll look into it.
    Are you using the Send() operation, or the SendIdoc() operation?
    Also, you are passing in a larger than allowed value for a particular column in one of the segments, right?
    Thursday, September 25, 2008 2:38 PM
  • We use the Send() operation.

    Yes we pass a larger than allowed value for a particular column in the IDOC. The adapter correctly fails with an error but memory leaks.

     

    Here's the error the adapter logs:

     

    Microsoft.ServiceModel.Channels.Common.XmlReaderParsingException: The length of the value for the field exceeds the allowed value. Value: 72  Field: NAME3 Allowed value: 70

    Thursday, September 25, 2008 2:46 PM
  • Is there a fix for this problem?

    Monday, October 27, 2008 10:49 AM
  • We've determined the cause of the memory leak, but it will occur only in error cases such as yours. If you fix your xmls so that they are indeed valid, you shouldn't see any leak.

     

    Monday, October 27, 2008 10:58 AM
  • So do you tell me that it is normal for Microsoft to have memory leaks in its products?

     

    Monday, October 27, 2008 11:37 AM
  • Rude statements like this will usually not give you any responses. However, I'll let this one pass.

     

    What is your scenario which requires you to send thousands of invalid IDocs to the adapter, which will cause exceptions to be thrown?

     

    Monday, October 27, 2008 12:28 PM
  • Whatever the reason for invalid IDOCs is, it is not a normal behaviour for the adapter to stop processing messages for this and other scenarios due to a memory leak.

     

    A good product would respond with an error but would not leak memory.

    Monday, October 27, 2008 12:41 PM
  •  

    Hi Raicho,

     

    You are absolutely right about your statement of a good product. We (Microsoft) do consider memory leak very seriously. We can try to fix this leak issue (if it is actually Adapter issue) in our next release however if you need immediate fix, I suggest you to work with our support team (PSS) and request for a QFE. The QFE request needs to have proper business justification so that MS can evaluate the priority of the request.

     

    Thanks,

    Koushik

     

     

    Wednesday, October 29, 2008 3:55 PM
  • Try doing this:

     

    (a) use the latest patch of the RFC SDK 7.0 Unicode (the latest patch was released on 5th May 2008).

    (b) set the environment variable (system wide environment variable, not per user) RFC_NO_DELTA = 1

     

    Reboot your machine, and retry your scenario. Does it help?

     

    Mustansir

     

    Thursday, October 30, 2008 6:04 AM