This section lists the following known issues with the Performance Advisor:
The management rules send notifications to the server log, but the logger for messages from the management rules subsystem itself is com.sun.enterprise.management.runtimetuner. By default, the log level for this logger is WARNING. To get more information from this logger, you must add a property to the configuration. The property name is com.sun.enterprise.management.runtimetuner and the value is FINE.
You can add this property on the Log Levels page in the Admin Console. For details, see the Admin Console online help.
You can also use the following asadmin set command to add this property. Substitute the name of the server instance or cluster for server. For example:
asadmin set server.log-service.module-log-levels.property.com\\.sun\\.enterprise\\.management\\.runtimetuner=FINE
For more information about the asadmin set command, see the Sun GlassFish Enterprise Server 2.1 Reference Manual.
The Performance Advisor is not supported on the AIX platform even though Sun GlassFish Enterprise Server version 2.1 is supported on the AIX platform.
The Admin Console does not tell you to restart the server after disabling and then re-enabling a rule. The rule is not enabled completely and alerts are not sent when user-specified thresholds are crossed.
After you disable and re-enable a management rule for a cluster or stand-alone server instance, you must restart the cluster or instance for the rule to take effect.
Dynamic reconfiguration is not supported for management rules.
After you create or change a management rule, you must restart the domain for the rule or the changes to take effect.
The value for the User Threshold of the GC Pause Time Alert shown in the server log and email is incorrect. The above-threshold data is reported correctly but the threshold is shown as ten times its actual value.
When the Tuner is evaluating whether a cluster is heterogeneous or homogeneous, it sometimes determines that a cluster is heterogeneous based solely on differences between machines in physical memory that are too small to be significant.
When the Linux AMD 64–bit JDK is used without the -d64 option, the server runs as a 64–bit server. However, without the -d64 option, the Tuner does not allow the maximum heap memory to be set above 1400 MB.
Add the -d64 option as a JVM option to the server or cluster you wish to tune. To use the Admin Console, go to the JVM Settings page for the configuration, select the JVM Options tab, select the Add JVM Option button, and enter the -d64 option. Or use the asadmin create-jvm-options command. For example:
asadmin create-jvm-options --target server \\-d64
For more information about the asadmin create-jvm-options command, see the Sun GlassFish Enterprise Server 2.1 Reference Manual.
When a rule is established on a cluster, and a new server instance is added to that cluster, the Maximum Pool Size (max-pool-size) setting is recalculated only for the newly created instance. The already existing instances are not synchronized with the latest information about the newly added instance.
Restarting the cluster synchronizes all server instances, and the Maximum Pool Size of the JDBC connection pool specified in the rule is applied across all instances.
When a JDBC Pool Manager rule is established on a cluster, Maximum Pool Size (max-pool-size) recalculation issues occur when * (applies to All Current and Future JDBC Connection Pools) is selected and a new JDBC connection pool is added to the cluster configuration. Since all pools are selected for automatic tuning, the Maximum Pool Size of the new pool is set to the default Maximum Pool Size setting instead of being calculated according to number of server instances present in the cluster. For example, suppose you have the following settings:
Default Max Connections: 100
Pool Name: * (applies to All Current and Future JDBC Connection Pools)
Max Connections: no value set
If there are two server instances in the cluster, then for all existing active JDBC connection pools, the Maximum Pool Size is recalculated to 50 by each of the instances. However, for any newly added JDBC connection pool, the Maximum Pool Size is recalculated to 100 by each of the instances.
Restart the cluster to recalculate the Maximum Pool Size for all JDBC connection pools on all server instances.
Selecting individual JDBC connection pool names with individual Max Connections values instead of selecting * (applies to All Current and Future JDBC Connection Pools) can prevent this issue in real-time production environments.