Microstrategy Web Server

[raktim]

Sometimes users of the Microstrategy Web Interface encounter an error
"java.lang.OutOfMemoryError". Then we were required to restart the Web
Server inorder to help the users get the reports again.
>From a Microstrategy Support Base we found out that such an error
occured because of an isuficient heap size of the Java Virtual Machine
which didnot allow the Microstrategy Web to handle large sets of data.
This can be handled by increasing the heap size allocated in the
following registry key HKEY_LOCAL_MACHINE\Software\MicroStrategy\JNI
Bridge\Configuration\JVM Options\HeapMaxSize.
I checked and found that for our web server the current heap size is
128 MB.
Can any one please advice on what parameters and by how much this heap
size can be increased.

[Renuka Aradhya]

hi ratkim,

checkout the MSTR support document file  # TN5600-8X-1993

its recomended to set the heap size between 256mb to 490mb.

MicroStrategy Web 8.x (ASPX)

The recommended value for HeapMaxSize is between 256 Mb and 490 Mb. Setting the JVM Heap Size above 490 Mb may cause the JVM to interfere with the ASP.NET heap size.

cheers
ronie..

[Chuy]

Raktim,

If the the physical memory size of the machine is at least 1GB, then go
with 512 MB, otherwise, at least make it 256MB.

There are many TN in MSTR KBase that talk about this. Check for example
TN5600-75X-1270 (this one is for 7.5x but even if you are using 8.x
versions, the same applies most of the time).

[Erdem Ozelmas]

Hi Raktim,

 

The general recommendation on this is to start by increasing the heap size to 512MB if the physical memory (RAM) on the server is 1GB or more. If this prevents the error, you're good. If not, depending on the amount of physical memory you have on the Web Server, you can increase it more but with caution. Please let the group know how this works out for you.

 

Erdem.


raktim <raktim....@gmail.com> wrote:

---

Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls. Great rates starting at 1¢/min.

[Mike]

I would recommend jumping up to 256 MB next. If you encounter the
problem again you could then go to 512 MB. You should also verify that
you have sufficient memory in the server while you are on the topic. A
good starting point would be roughly 2 GB of memory.