Adaxes Service Memory Consumption

Question

Hi

I notice regularly that Adaxes Service memory increase to max. allowed : ( about 8 Gb allowed) and stay until I restart the service (sometimes some days without unloading)

With no particular activity or load on the server.

https://drive.google.com/file/d/0B7-4lG ... sp=sharing

Our configuration :
Windows Server 2012 Std
8 Gb RAM
2 Intel Xeon X5650 @ 2.67 GHz (x64)
Adaxes 2013.2

Have you got any idea ?

Best regards

Answer 1

Hello,

This can be caused by many reasons. The first thing you should look at are automation means, such as Business Rules, Custom Commands or Scheduled Tasks. If they, for example, launch PowerShell scripts, and the scripts do not release resources correctly, this can be a cause for the issue.

To troubleshoot the issue, note the time when aggressive memory consumption starts, and take a look at Adaxes Service Log for events that occur approximately at that time and can cause such an issue. For information on how to view Adaxes Service Log, see the following help article: http://www.adaxes.com/help/?Logging.Vie ... eLogl.html.

Comments

Hi,

I tried to correlate actions from Adaxes log and memory usage increases with no succes.
Memory usage increase in different case (and often on "built in" actions like user update).
It seems that there's no "memory release".

Have you got other sggestions ?
Many Thanks

Regards

---

Hello,

Can you send the following to our support e-mail (support[at]adaxes.com):

1. Adaxes Event Log. For information on how to access it, see Service Event Log.
2. Logging database of Adaxes Service Log. The database storage file is called AdaxesLog.db3 and is located in the LogDB subfolder of the folder where the Adaxes service is installed.
3. Time when memory consumption started so we could correlate it with events in the logs. Preferably, at least a couple of examples would be good (the more, the better).

---

Hi all,

After a long time, and some improvements in my powershell scripts, I solved my issue.
For your information, you were right on the fact that some scripts did not release resources correctly, in particular not closed remote session.

Thanks for your help again

Regards

---

Hello,

Thanks for the update!