RE: [Axapta-Knowledge-Village] RE: Posting Memory Leak

Thu, 28 Jul 2005 06:20:24 -0700

Title: Message
We are running Ax v3 SP2.
-----Original Message-----
From: Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Jesper Kehlet
Sent: Thursday, 28 July 2005 15:02 PM
To: Axapta-Knowledge-Village@yahoogroups.com
Subject: RE: [Axapta-Knowledge-Village] RE: Posting Memory Leak

What version of Axapta is this?  Application?  Kernel?

From: Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Edine Le Roux
Sent: Thursday, July 28, 2005 5:15 AM
To: Axapta-Knowledge-Village@yahoogroups.com
Subject: [Axapta-Knowledge-Village] RE: Posting Memory Leak

We downloaded and installed the MDAC 2.8 version. The posting memory leak still exist at +-150k per Sales Order posted.
 
Post: Posting Memory Leak
 
The problem is that we have identified that there are definitely memory leaks in the posting process leading to a leak of (on average) 150k with each call to SalesFormLetter.post(), which we did not notice previously due to the fact that our posting pattern was different. Basically things have changed as follows due to changed business requirements:

Before:
-Import batches of 500 Sales Orders into parm tables
-Post all 500 simultaneously

Now
-Import a single invoice 'realtime'
-Post the invoice

As a result, when posting all 20000 invoices using the old method, we would only leak 20000/500*150k = 6000k = about 6Mb, which is by no means trivial, but small enough to not cause leak problems too often (though in retrospect some of our memory issues now make sense. Now when importing 20000 invoices we are leaking 20000*150k = 3000000k = about 3Gb! We are currently running into issues after 3500 invoices, which leaks about 500M, which matches the behaviour on Edine's machine.

We are aware that the SmartHeap garbage collector may eventually reclaim some of this memory, but by that time we have already experienced out of memory issues, ie Axapta has already crashed.

Our requirements are that we need to import single invoices and post
them immediately and return the generated voucher numbers. This,
combined with the fact that we cannot have entire batch postings failing due to one invalid invoices means that we cannot stick to a batched approach of any kind. We MUST have a 1-1 relation between invoices and posts.

What we want to know is if anyone has written any code to fix this leak, or if anyone knows how to fix this.

Regards,
   Hennie


Sharing the knowledge on Axapta.


YAHOO! GROUPS LINKS



Reply via email to