TUNE

TUNE0101W: Based on the CPU utilization, the system does not appear to be under load. Please run the performance advisor with a representative workload. {0}
TUNE0201W: The rate of discards from the prepared statement cache is high. Increase the size of the prepared statement cache for the data source {0}. {1}
TUNE0202W: Increasing the {0} thread pool''s Maximum Size to {1} may improve performance. {2}
TUNE0203W: Based on the number of processors, the {0} thread pool is unusually large. {1}
TUNE0204W: Decreasing the size of the {0} by setting the the minimum size to {1} and the maximum size to {2} may improve performance. {3}
TUNE0205W: Increasing the {0} by setting the minimum size to {1} and the maximum size to {2} may improve performance. {3}
TUNE0206W: Decreasing the connection pool for data source {0} by setting the minimum size to {1} and the maximum size to {2} may improve performance. {3}
TUNE0207W: Utilization of the connection pool is high. Performance might be improved by increasing the maxPoolSize for data source {0}. Try setting the minimum size to {1}, and the maximum size to {2}. {3}
TUNE0208W: Data source {0} does not seem to be in use. If the data source is used occasionally, then decrease the number of connections in the pool, by setting minConnections to {1}, and maxConnections to {2}. If the data source is never used, then delete the data source. {3}
TUNE0210W: Writing persistent sessions is unusually slow for {0}. {1}
TUNE0211W: The sessions being written to the session repository for {0} are unusually large. {1}
TUNE0212W: Reading persistent sessions is unusually slow for {0}. {1}
TUNE0213W: The sessions being read by {0} from the session repository are unusually large. {1}
TUNE0214W: The session cache for {0} is smaller than the average number of live sessions. Increasing the session cache size to at least {1} may improve performance. {2}
TUNE0215W: Increasing the session cache for {0} will reduce the number of invalid sessions returned by getSession and should increase performance. Given the current rate of errors and average session lifetime, increase cache size to {1}. {2}
TUNE0216W: There is not enough memory to change settings. {0}
TUNE0217E: Unknown data type. {0}
TUNE0218W: The dynamic cache instance {0} is not large enough to store all cacheable results. Consider increasing the number of cache entries to {1}.
TUNE0219W: The dynamic cache instance {0} is not currently using all the available entries. Consider decreasing the number of cache entries to {1}.
TUNE0220W: The Java virtual machine is spending a considerable amount of time in garbage collection. Consider increasing the heap size. {0}
TUNE0221W: Data for memory session size is not available for certain Web applications. {0}
TUNE0222W: The sessions in the session cache of Web application {0} average {1}K, which is unusually large. {2}
TUNE0223W: There is at least one session in the session cache of Web application {0} which is {1}K. {2}
TUNE0224W: Consider lowering the monitoring level from Maximum to High for the modules listed below. {0}
TUNE0301W: The percent of connections used in the connection pool is optimal. {0}
TUNE0302W: The current size of the connection pool is not equal to the minimum value and does not decrease the size of the pool. {0}
TUNE0303W: Number of threads working in {0} is low, but the system does not seem to be under stress. {1}
TUNE0304I: No problem detected with the {0}. {1}
TUNE0305I: Since the CPU is heavily utilized, increasing the number of threads in {0} does not improve performance. {0}
TUNE0306I: The current average thread pool size: {0} is less than the current threshold. {1}
TUNE0307I: The session cache ratio of (live sessions)/(session cache size) is good. {0}
TUNE0308I: The session cache for {0} is large enough to contain the average number of live sessions. {1}.
TUNE0309I: The ratio of live sessions and session cache size is small enough that resources are not wasted. {0}
TUNE0310I: The size of the session objects written by the application server, for {0} are within reasonable limits. {1}
TUNE0311I: The size of the persistent store session objects that are read by the application server for {0} are within reasonable limits. {1}
TUNE0312I: The time taken to read session objects is reasonable for {0}. {1}
TUNE0313I: The time taken to write session objects for {0} is reasonable. {1}
TUNE0314I: In the current interval, there is room available in session cache for new sessions of Web Application {0}. {1}
TUNE0315I: The prepared statement cache is set appropriately for data source {0}. {1}
TUNE0316I: The size of the {0} is invalid. The pool size is {1}; there are {2} active threads. {3}
TUNE0317I: No further tuning problems have been found. {0}
TUNE0318I: There is no data available for data point {0}. If the problem persists, check the Performance Monitoring Infrastructure (PMI) settings. {1}
TUNE0319W: Unable to completely utilize the performance advisor because data collection is not enabled for some modules. Enable monitoring for the specified modules. {0}
TUNE0320W: Unable to completely utilize the performance advisor because the Performance Monitoring Infrastructure (PMI) is not enabled for this server. Enable the Performance Monitoring Infrastructure (PMI) using the administrative console and restart the server. {0}
TUNE0321W: Not enough data to perform analysis. {0}
TUNE0322W: The Runtime Performance Advisor is not running. Restart the application server. {0}
TUNE0323W: There was a general error detected in the Runtime Performance Advisor. Check the application server logs. {0}
TUNE0324W: There was an unknown error detected in the Runtime Performance Advisor. Check the application server logs and enable trace. {0}
TUNE0325I: Enough dynamic cache entries are allocated. {0}
TUNE0326I: There are no problems with the amount of time spent garbage collecting. {0}
TUNE0327I: There are no problems with the in-memory session size. {0}
TUNE0328W: Unable to completely utilize the performance advisor because the Performance Monitoring Infrastructure (PMI) is not enabled for this nodeagent. Enable the Performance Monitoring Infrastructure (PMI) using the administrative console and restart the nodeagent. {0}
TUNE0401E: There was an exception getting an AdminClient {0}.
TUNE0402E: Runtime Performance Advisor could not register for notifications for {0}. The error reported was {1}.
TUNE0403E: Runtime Performance Advisor caught a class cast exception when processor AttributeChangedNotification. The following notification should be sent back as an AttributeChangeNotification rather than a normal Notification: {0}. The error reported was {1}
TUNE0404E: Runtime Performance Advisor could not find the attribute {0} on mbean {1}
TUNE0405E: Runtime Performance Advisor could not register for regisration/unregistration notifications on the MBeanServerDelegate for type {0}. The error reported was {1}.
TUNE0406E: The attribute {0} is not available from the mbean {1}. The Runtime Performance Advisor will use the repository configuration in it''s place.
TUNE0407E: Could not refresh repository cache .
TUNE0408E: Could not refresh {0} Configuration.
TUNE0409E: could not get {0} resource from config root.
TUNE0410E: There was a general error detected in the Runtime Performance Advisor. Check the application server logs. {0}
TUNE0999W: Encountered an error while running performance advisor. {0}
TUNE5001W: JVM initial heap size is unusually small. Typically, the initial heap size is greater than or equal to {0}.
TUNE5002W: The JVM initial heap size is unusually large. Typically, the initial heap size is no more than {0}.
TUNE5003W: The JVM maximum heap size is unusually small. Typically, the maximum heap size is greater than or equal to {0}.
TUNE5004W: The JVM maximum heap size is unusually large. Typically, the maximum heap size is no more than {0}.
TUNE5005W: The initial JVM heap size is greater than the maximum heap size. {0}
TUNE5006W: The JIT is disabled on the JVM. {0}
TUNE5007I: The JIT is enabled on the JVM. {0}
TUNE5008W: Trace Specifications are enabled. {0}
TUNE5011W: The size of the minimum thread pool for the Web container is greater than the size of the maximum thread pool. Adjust the sizes so that the minimum thread pool is equal to or less than the size of the maximum thread pool. {0}
TUNE5012W: The size of the minimum thread pool for the Web Container is unusually large. Typically, the minimum thread pool size of the Web container is no more than {0}. {1}
TUNE5013W: The size of the maximum thread pool for the Web container is unusually large. Typically, the maximum thread pool size of the Web container is no more than {0}. {1}
TUNE5021W: The size of the minimum thread pool for the ORB is greater than the size of the maximum thread pool. Adjust the sizes so that the minimum thread pool size is equal to or less than the size of the maximum thread pool. {0}
TUNE5022W: The size of the minimum thread pool for the ORB is unusually large. Typically, the minimum thread pool size is no more than {0}. {1}
TUNE5023W: The size of the maximum thread pool for the ORB is unusually large. Typically, the maximum thread pool size is no more than {0}. {1}
TUNE5031W: The minimum pool size for the data source is greater than the maximum pool size for data source {0}. Adjust the sizes so that the size of the minimum connection pool is no more than the size of the maximum connection pool. {1}
TUNE5032W: For data source {0}, the minimum connection pool size is unusually large. Typically, the connection pool size should be no larger than {1}. {2}
TUNE5033W: For data source {0}, the maximum connection pool size is unusually large. Typically, the connection pool size is no more than {1}. {2}
TUNE5034W: The prepared statement cache is unusually large for data source {0}. Typically, the prepared statement cache is no more than {1} statements per connection. {2}
TUNE5035W: Run the DB2 Performance Configuration Wizard for advice on tuning DB2 databases for performance.
TUNE5041W: Enable dynamic caching for better performance. Enable dynamic caching using the administrative console. {0}
TUNE5042W: Enable servlet caching for better performance. {0}
TUNE5901W: An error occurred while reading the configuration for {0}. {1}
TUNE9001W: Heap utilization patterns indicate that you may have a memory leak {0}.
TUNE9002W: Though the heap has room for expansion there are early warning signs of a memory leak {0}.
TUNE9003I: There did not appear to be a GC cycle in the heap. Clearing current data structure. {0}.
TUNE9004I: No memory leak detected {0}.
TUNE9005I: The following suspious memory warning has been detected. {0}.
TUNE9006W: It has been determined that a previous suspicous memory usage notification was in error. No memory problem has been detected at this time. {0}
TUNE9007W: It has been detected that your java heap is getting large relative to memory pool size. A memory leak is possible. The effective memory pool {2} is {0} and your java process size has grown to be {1}. The period analyzed is between {3} and {4}. {5}.
TUNE9008I: No problem has been detected with the java heap being large relative to the memory pool size. The effective memory pool {2} is {0} and the java process size has grown to be {1}. The period analyzed is between {2} and {3}. {5}.


Terms and conditions for information centers | Feedback

Last updated: November 13, 2013 05:41 AM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-mp&topic=com.ibm.ws.performance.tuning.properties.perftuning.dita
File name: com.ibm.ws.performance.tuning.properties.perftuning.html