It's all about the answers!

Ask a question

Anyone experience issues with RAM not being released in a MS SQL server (V2012)?


Timothy Miller (13314) | asked Mar 04 '16, 3:24 p.m.

Our CLM 5.0.2 release is driving a MS SQL backend with 6 cores and 64GB of RAM out of memory >95% . The DBA tells me that the application is not releaseing connections.

We believe the problem stems from users requesting "comprehensive" type reports that build PDF reports (some in excess of 230 pages) also the extract of data to .csv files.

There is also a question regarding the two icons on the report status screen (Cancel and DELETE). We would like to know the activities that both of the functions perform and if there is a particuar order that one performs when executed.

2 answers



permanent link
Michael Triantafelow (4513) | answered Mar 07 '16, 2:19 p.m.
A comprehensive PDF should not be able to exhaust your server's memory.  While these jobs seem big, they are broken down into small chunks and (by default) only 4 of those small chunks are allowed into memory at any one time.  I've personally generated 100,000+ page PDF documents with only an 8GB heap.

That said, it is entirely possible you have found some unique edge case where there is a bug.  I suggest that you formally engage with support so that we can help you get to the bottom of this quickly.

To answer your questions about cancel and delete: it is useful to think about the items you see in that UI as "jobs".  The cancel button tells the Export Framework to stop working on the selected job(s).  The job(s) will remain in the queue (and in your repository) but will show its status as "canceled".  Delete on the other hand removes the job from the queue (and the repository) entirely.  

Also, note that jobs "expire" after a period of time (default is 48 hours).  At that point QM will delete them from the repository on its own without your intervention.

permanent link
Donald Nong (14.5k614) | answered Mar 06 '16, 7:04 p.m.
This is kind of expected. CLM maintains a JDBC connection pool, which contains a set number of database connections. I can't find any documents stating how often these connections get recycled (maybe never). The below links may help you understand a bit better.
https://jazz.net/library/article/1484
https://jazz.net/forum/questions/215859/is-there-a-way-to-see-the-mediator-and-jdbc-pool-resource-consumption

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.