LAE

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: michael_w_mds

Hi,

Since installing JDK 6, the server wont connect and is complaining about the VM.

I've tried reinstalling the software but I still have the same issue.

See the attached screenshot for error details.


Any ideas on how to fix this?



Thanks,
Mike.
Attachments:
server.JPG

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: BrianQ2

I'm also having this issue. Is there a solution?

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: Tim Meagher

Hi,

Sorry about the long delays about posting a response to this topic. I only came across this post yesterday. Hopefully you have been in touch with your MDA support representative and figured out a solution that works for you for this problem.

This is an issue that we are aware of - and has an internal issue number of 3016 for your reference. So far, it appears to only occur for some people and is not overly common. Strangely, where this is occurring is on machines having similar specifications to where no problems are noticed.

It appears that the problems are occurring due to the -Xmx parameter being passed to initialize the JVM when launching the LAE server. It isn't an option to remove the -Xmx setting, as the default value (based on system configuration) used by the JVM will often be insufficient and result in OutOfMemoryErrors.

In general, the JVM initialization errors reported will occur because the amount of memory requested is larger than the amount of physical memory available. Strangely, this has been noticed on some machines with a much larger amount of physical memory available than the -Xmx parameter is asking for. Since the error is occuring prior to the LAE initializing, and can be reproduced from the command line on the machines in question without attempting to use the LAE it seems like there might be a Windows<->Java issue.

It is possible that no initial heap size is being asked for, and this ends up with the JVM requested the maximum heap size on initialization. However even in this case, there should be enough memory available for the JVM to initialize using the max heap size.

With issues like this it is best to contact your MDA support representative, as the solution to the problem may be different from instance to instance and may involve some investigative work (running dummy programs to determine what an acceptable -Xmx value is for your system etc) and changes specific to your needs.

On the plus side, these issues have been noted, and while it is impossible to ensure that all operating systems will always grant the amount of memory requested, these settings will be much more transparent and easier to configure using the standard configuration files in later releases to ensure that these problems are easier to resolve.

Regards,
Tim Meagher.

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: mermacora

I've had another user report the same error with Lavastorm Desktop v4.5.2 on a Windows XP machine with 1GB RAM.
Would appreciate any suggestions to resolve this.

Thanks,
Mario

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: mermacora

In fact, this problem was experienced with Lavastorm Desktop v4.5.1 and only after the user upgraded to Internet Explorer 8. The user also experienced problems with other installed applications after the IE8 upgrade and has since arranged for a new PC with more memory.

However, the below was provided by the MDS Lavastorm Support team as the recommended way to work around this problem...

Try a few different JVM memory heap size adjustments to see what works. This adjustment can be made in the following configuration file:

%LAE_HOME%\conf\brain\ls_brain.prop

Edit that file and add the following parameter under the "General brain properties" section somewhere (location doesn't matter functionally, but this location would make sense). Save the file and restart the server to see if the problem is resolved.

ls.brain.server.javaMaxHeapSize=960M

I believe the default setting is 1024M, so if the above adjustment does not work, I would try lowering it incrementally by factors of 8 until the problem is resolved e.g.:

ls.brain.server.javaMaxHeapSize=896M
ls.brain.server.javaMaxHeapSize=832M
ls.brain.server.javaMaxHeapSize=768M

Please try this a handful of times, keeping a record of each of the setting changes.