Please see Julian Buss web site for explanation: www.juliusbuss.de/web/youatnotes/blog-jb.nsf/dx/huge-memory-leak-in-xpages-engine.htm?opendocument&comments

 

I posted a memory issue I was having with a repeat control a few days ago, but I have reposted as I am getting the same problem, regardless of what is on the XPage.

http://www-10.lotus.com/ldd/xpagesforum.nsf/topicThread.xsp?action=openDocument&documentId=BC190CA7B2AFC6488525793C005EE030

Domino 8.5.1 FP5 HF139 on Windows 2008 R2 standard and Domino 8.5.3 on local PC, Windows 7.

We have a web application that has been in production for about a year now, HTTP access, using a mix of traditional and XPage (backing beans and XPage "agents" to serve up data to traditional web pages and external systems via RESTful urls, dojo.xhrGet(), etc.).  The application is used 365\24\7 (mulitple clustered servers).

We are in process of converting some traditional pieces over to XPages (at this stage views, so we can make use of paging), but I have run into a fundamental memory issue, which I am hoping someone might be able to advise me on.  I have created XPages that appeared to have memory issues, so stripped everything back to basics.  I have created an xpage as follows, as simple as you can get

<?xml version="1.0" encoding="UTF-8"?>
<xp:view xmlns:xp="http://www.ibm.com/xsp/core">
    <b>Hello</b>everyone.
</xp:view>

Now start task manager and watch the nhttp task, every time you open the xpage via your url, the memory jumps up in pretty much exactly 256k steps, this memory is not released.  I have tested this on Domino 8.5.1 FP5 HF139 on Windows 2008 R2 standard and Domino 8.5.3 on my local PC, same results.  We still have a "gradual" memory leak on our production servers, we extensively use backing beans accessed via our XPage "agent".  We have spent a long time debuging the backing beans, checking for recycling etc., our memory issue might actually be just acessing the Xpage agent page...I will follow up on this when I have results.

In application settings, I changed Server page persistence to Keep pages on disk (thanks Tommy Valand http://www-10.lotus.com/ldd/xpagesforum.nsf/topicThread.xsp?action=openDocument&documentId=BC190CA7B2AFC6488525793C005EE030).  It doesn't seem to make any diff which setting I choose.

I just have to be missing something fundamental, other people would have noticed this by now, does anyone have any ideas?  Over the course of an 8 hour shift, our server would run out of memory very quickly.

Regards,

Nick