Problem: GUI hangs (or unexpected behavior) when trying to load a large configuration file

When using lbadmin or Web administration (lbwebaccess) to load a large configuration file (roughly 200 or more add commands), the GUI may hang or display unexpected behavior, such as responding to screen changes at an extremely slow rate of speed.

This occurs because Java™ does not have access to enough memory to handle such a large configuration.

There is an option on the runtime environment that can be specified to increase the memory allocation pool available to Java.

The option is -Xmxn where n is the maximum size, in bytes, for the memory allocation pool. n must be a multiple of 1024 and must be greater than 2MB. The value n may be followed by k or K to indicate kilobytes, or m or M to indicate megabytes. For example, -Xmx128M and -Xmx81920k are both valid. The default value is 64M. Solaris 8 has a maximum value of 4000M.

For example, to add this option, edit the lbadmin script file, modifying "javaw" to "javaw -Xmxn" as follows. For AIX® systems, modify "java" to "java -Xmxn".

There is no recommended value for n , but it should be greater than the default option. A good place to start would be with twice the default value.



Terms and conditions for information centers | Feedback

Last updated: September 10, 2012 09:00 AM EDT
File name: ttrb_guihang.html