perf.tuning.dynacache.entries.decreaseEntries=TUNE0219W: The dynamic cache instance {0} is not currently using all the available entries. Consider decreasing the number of cache entries to {1}. The dynamic cache is not using all the available entries. If the server is operating under normal load, consider reducing the number of dynamic cache entries so that these resources can be allocated elsewhere. perfalert.restart=TUNE0322W: The Runtime Performance Advisor is not running. Restart the application server. {0} To use the Runtime Performance Advisor, restart your Application Server. From the Application Server installation directory, go to the bin directory and type stopserver.bat command to stop the server and then type thestartserver.bat command to start the server. perf.tuning.jvm.tooLongInGc=TUNE0220W: The Java virtual machine is spending a considerable amount of time in garbage collection. Consider increasing the heap size. {0} There are many reasons why an application might spend too much time in garbage collection. Often, it indicates an application with many short-lived objects. However, it can also indicate a heap that is too small, causing the Java Virtual Machine (JVM) memory manager to thrash. Increasing the heap size might help in this case, by lengthening the time between garbage collection calls, but might also increase the time needed for each garbage collection. perfalert.session.writeTimeTooLarge=TUNE0210W: Writing persistent sessions is unusually slow for {0}. {1} Your session repository might have a problem, your sessions might be too large or you might be writing to the repository more often than necessary. If you use multi-row sessions, the times are per attribute rather than per session. Consult the application provider about reducing the session size. perfalert.Exception.couldNotRefreshRepositoryCache=TUNE0407E: Could not refresh repository cache . There was a problem getting the Application Server configuration details from the repository. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . perfalert.exception.stacktrace=TUNE0999W: Encountered an error while running performance advisor. {0} The performance advisor created an error. Restart performance advisor. perfalert.memoryLeak.noGCCycle=TUNE9003I: There did not appear to be a GC cycle in the heap. Clearing current data structure. {0}. There did not appear to be a GC cycle. The application does not appear to be in use. No action is required perfalert.session.writeTimeOk=TUNE0313I: The time taken to write session objects for {0} is reasonable. {1} This message is for informational purposes only. No action is required. perfalert.connPool.usageHigh=TUNE0301W: The percent of connections used in the connection pool is optimal. {0} The connection pool size is fine and the pool usage is good. No action is required. perfalert.session.increaseCacheSize=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} In this situation, the overflow session cache is used instead of the main session cache, possibly slowing performance. Check that the session growth is bounded. In general, the average number of live sessions is approximately the rate of session creation times the average lifetime of a session. To tune session management, open the administrative console and click Servers > Application Servers > Server > Web Container Settings > Web Container > Session Management. perfalert.connPool.toolarge=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} Decreasing the size of connection pool supports better pooling and frees memory resources. To decrease the size of connection pool, open the administrative console and click Resources > JDBC Providers > JDBC_provider > Data Sources > data_source > Connection pool properties. perf.tuning.session.size.noProblem=TUNE0327I: There are no problems with the in-memory session size. {0} The in-memory session sizes are all reasonable. No action is required. perfalert.memoryLeak.unboundedHeap.noProblem=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}. Memory usage patterns do not indicate a memory leak No action is required perfalert.session.alwaysRoomForSession=TUNE0314I: In the current interval, there is room available in session cache for new sessions of Web Application {0}. {1} Session cache size is good. No action is required. perf.tuning.jvm.gc.noProblem=TUNE0326I: There are no problems with the amount of time spent garbage collecting. {0} This message is for informational purposes only. No action is required. perfalert.unknownError=TUNE0324W: There was an unknown error detected in the Runtime Performance Advisor. Check the application server logs and enable trace. {0} The Runtime Performance Advisor created an error. Locate the log files under the installation root > logs directory. Each server instance has its own directory in the logs directory. Enable tracing in the administrative console by clicking Application Servers > server > Logging and Tracing > Diagnostic Trace Service. cfgAlert.trace.TraceSpecificationEnabled=TUNE5008W: Trace Specifications are enabled. {0} Enabled trace specifications might significantly reduce the performance of the Application Server. To disable unwanted trace specifications, open the administrative console and click Application Servers > server > Change Log or Trace Levels and disable all unwanted trace specifications cfgAlert.jvmConfig.JITEnabled=TUNE5007I: The JIT is enabled on the JVM. {0} This message is for informational purposes only. No action is required cfgAlert.connPoolConfig.maxPoolSizeTooBig=TUNE5033W: For data source {0}, the maximum connection pool size is unusually large. Typically, the connection pool size is no more than {1}. {2} In general, a very large connection pool reduces performance, although it might be necessary for some applications. To change the connection pool properties, open the administrative console and click JDBC Providers > JDBC_provider > Data Sources > data_source > Connection pool properties. See the information center for more information about queueing. perfalert.Exception.couldNotRegisterForNotification=TUNE0402E: Runtime Performance Advisor could not register for notifications for {0}. The error reported was {1}. The Runtime Performance Advisor failed to register for notifications of runtime changes. If you are running in a network deployment environment, make sure that the deployment manager is still running. perfalert.pool.noProblem=TUNE0304I: No problem detected with the {0}. {1} Connection pool size is good. No action is required. perfalert.Exception.couldNotFindResource=TUNE0409E: could not get {0} resource from config root. There was a problem getting the resource from the configuration root. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . perf.tuning.session.size.avgTooBig=TUNE0222W: The sessions in the session cache of Web application {0} average {1}K, which is unusually large. {2} Large sessions can reduce performance. The major costs are serialization and the amount of memory that is used. Consider revising your application to reduce the average session size. cfgAlert.dynamicCache.enableDynamicCache=TUNE5041W: Enable dynamic caching for better performance. Enable dynamic caching using the administrative console. {0} Dynamic cache is not enabled. To enable dynamic cache service, open the administrative console and click Servers > Application Servers > server > Container Services > Dynamic Cache Service. See the information center for more information on using dynamic cache service. cfgAlert.connPoolConfig.minGreaterThanMax=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} The value specified for the minimum connection pool of the data source is greater than the maximum pool size. To change the connection pool properties, open the administrative console and click JDBC Providers > JDBC_provider > Data Sources > data_source > Connection pool properties. See the information center for more information about queueing. perf.tuning.session.size.maxTooBig=TUNE0223W: There is at least one session in the session cache of Web application {0} which is {1}K. {2} Large sessions can reduce performance. The major costs are serialization and the amount of memory used. Consider revising your application to reduce the average session size. perfalert.NoDataType=TUNE0217E: Unknown data type. {0} Data access is not available for this data type. See the Troubleshooting section of the information center. perf.tuning.dynacache.entries.noProblem=TUNE0325I: Enough dynamic cache entries are allocated. {0} This message is for informational purposes only. No action is required. perfalert.advisor.noPmiData=TUNE0319W: Unable to completely utilize the performance advisor because data collection is not enabled for some modules. Enable monitoring for the specified modules. {0} Performance Monitoring Infrastructure (PMI) is not enabled for some modules. To fully utilize the performance advisor, enable monitoring for these modules. To enable PMI from the administrative console, click Application Servers > server > Performance Monitoring Infrastructure (PMI). Note: Setting the JVM module to MAX requires enabling the Java Virtual Machine Profiling Interface (JVMPI). See the information center for more information on this topic. perf.tuning.dynacache.entries.increaseEntries=TUNE0218W: The dynamic cache instance {0} is not large enough to store all cacheable results. Consider increasing the number of cache entries to {1}. When the dynamic cache is not large enough, the server must recalculate the evicted entries. However, in many systems, there is not enough memory in the heap for a cache large enough to hold all cacheable entries. Use the Tivoli Performance Viewer or other monitoring software to watch heap utilization as you adjust the dynamic cache size. perfalert.Exception.adminClient=TUNE0401E: There was an exception getting an AdminClient {0}. Performance Runtime Advisor expected to get an administrative client and did not. Check that the node agent is running and that process discovery has occurred on the application server. perfalert.Exception.couldNotRefreshConfiguration=TUNE0408E: Could not refresh {0} Configuration. There was a problem getting the Application Server Session configuration details from the repository. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . perfalert.SystemNotUnderLoad=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} If the system is meant to be under load, there might be a bottleneck within the application itself ( for example, over synchronization ), or elsewhere in the system. If this problem occurs in a test environment, the load driver might have reached its maximum limit. Consult the information center for more information on deadlocks and application performance tuning. perfalert.Exception.mBeanAttributeNotAvailable=TUNE0406E: The attribute {0} is not available from the mbean {1}. The Runtime Performance Advisor will use the repository configuration in it''s place. The Runtime Performance Advisor uses the runtime settings to help determine performance problems. This data was not available so that persistent configuration is used instead of the runtime configuration. No action is required. perfalert.session.readSizeTooLarge=TUNE0213W: The sessions being read by {0} from the session repository are unusually large. {1} Large sessions can reduce performance. The major costs are serialization, communication with the repository and the amount of memory used. Consider revising your application to reduce the session size. cfgAlert.jvmConfig.initialHeapTooSmall=TUNE5001W: JVM initial heap size is unusually small. Typically, the initial heap size is greater than or equal to {0}. If the initial Java Virtual Machine (JVM) heap size is too small, the heap has to expand more often than required and performance degrades when the application server is first initialized. To change the JVM heap size, open the administrative console and click Application Servers > server > Java and Process Management > Process Definition > Java Virtual Machine. See the information center for more information on tuning JVM. perf.tuning.session.unpersisted.webapp.noData=TUNE0221W: Data for memory session size is not available for certain Web applications. {0} Session size contributes to application performance. If the data is available, the performance advisor gives advice on the average session size. Enable the Performance Monitoring Infrastructure (PMI) SessionObjectSize counter if you are not in a distributed environment. perfalert.connPool.notInUseOrtoolarge=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} The system appears to be under heavy load (CPU is very busy,) yet the number of threads used within the pool is small. Decreasing the size of the thread pool might free resources and might improve performance. To decrease the size of connection pool, open the administrative console and click Resources > JDBC Providers > JDBC_provider > Data Sources > data_source > Connection pool properties. perfalert.pool.initialMaxSmall=TUNE0202W: Increasing the {0} thread pool''s Maximum Size to {1} may improve performance. {2} When a growable thread pool expands beyond the maximum size, those additional threads cannot be reused and can be discarded from the pool. Increasing the thread pool maximum size to the average pool size can improve performance significantly. If this message appears repeatedly, look for continued growth of the thread pool, which often indicates a leak or deadlock. To increase the thread pool size for the Web container in the administrative console, click Servers > Application Servers > server > Thread Pools. To increase the thread pool size for the ORB Service, click Servers > Application Servers > server > Container Services > ORB Service > Thread Pool. cfgAlert.connPoolConfig.prepStmtCacheTooBig=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} A large prepared statement cache is usually a problem only if memory is constrained and there are many infrequently used prepared statements. In this case, the statements are not discarded, but consume memory. In general, the size of the cache equals the number of prepared statements used in the application. To change the size of the cache, open the administrative console and click JDBC Providers > JDBC_provider > Data Sources > data_source. See the information center for more information about queueing. perfalert.pool.increase=TUNE0205W: Increasing the {0} by setting the minimum size to {1} and the maximum size to {2} may improve performance. {3} The utilization of the thread pool is high, yet the CPU utilization is low. The thread pool size might be too small and might be unnecessarily limiting the performance of your system. Increasing the size of the pool can also reduce performance. Test carefully. You can obtain optimal performance when the thread pool size is large enough to support full CPU utilization. It is normal to see high utilization of the thread pool. To change the thread pool size for the Web container in the administrative console, click Servers > Application Servers > server > Thread Pools. To increase the thread pool size for the ORB Service, click Servers > Application Servers > server > Container Services > ORB Service > Thread Pool. perfalert.advisor.pmiDisabledNodeagent=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} The Performance Monitoring Infrastructure (PMI) is not enabled for this node agent. To enable the PMI from the administrative console, click System Administration > Node Agents > nodeagent > Performance Monitoring Infrastructure (PMI).Select the Enable Performance Monitoring Infrastructure (PMI) option, click Apply and restart the node agent. perfalert.session.readSizeOk=TUNE0311I: The size of the persistent store session objects that are read by the application server for {0} are within reasonable limits. {1} This message is for informational purposes only. No action is required. cfgAlert.dynamicCache.enableServletCache=TUNE5042W: Enable servlet caching for better performance. {0} Servlet caching is not enabled. To enable servlet caching in the administrative console, click Servers > Application servers > server_name > Web container settings > Web container and select Enable servlet caching under the Configuration tab. Click Apply or OK. You must restart your Application Server. cfgAlert.jvmConfig.initialGreaterThanMax=TUNE5005W: The initial JVM heap size is greater than the maximum heap size. {0} The Java Virtual Machine (JVM) heap size settings specify an initial heap size that is larger than the maximum heap size. To change the JVM heap size, open the administrative console and click Application Servers > server > Java and Process Management > Process Definition > Java Virtual Machine. See the information center for more information on tuning JVM. perfalert.memoryLeak.memoryLeakWarning=TUNE9002W: Though the heap has room for expansion there are early warning signs of a memory leak {0}. Over a period of time the amount of free memory appears to be decreasing or there is consistently insufficient free memory in the heap, indicating that you may have a memory leak. Use tooling to further analyze your memory useage over time. Refer to the information center for more information about diagnosing out-of-memory errors and java heap memory leak. perfalert.advisor.pmiDisabled=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} The Performance Monitoring Infrastructure (PMI) is not enabled for this server. To enable PMI from the administrative console, click Application Servers > server > Performance Monitoring Infrastructure (PMI). Select the Enable Performance Monitoring Infrastructure (PMI) option, click Apply and restart your server. perfalert.pool.decrease=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} The CPU utilization of the system is high. Decreasing the size of the thread pool might free resources and might improve performance. To decrease the thread pool size for the Web container in the administrative console, click Servers > Application Servers > server > Thread Pools. To increase the thread pool size for the ORB Service, click Servers > Application Servers > server > Container Services > ORB Service > Thread Pool. perfalert.session.noRoomForNewSession=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} When the session cache is full and cannot overflow, the getSession() method might return an invalid session. The average number of live sessions is approximately the rate of session creation times the average lifetime of a session. If this situation was caused by a temporary load surge, consider allowing the cache to overflow. Note that if an application has unbounded session growth, allowing overflow might result in a memory leak. To tune session management, open the administrative console and click Servers > Application Servers > Server > Web Container Settings > Web Container > Session Management. perfalert.prepStmt.message_correct=TUNE0315I: The prepared statement cache is set appropriately for data source {0}. {1} This message is for informational purposes only. No action is required. perfalert.pool.initialMaxOk=TUNE0306I: The current average thread pool size: {0} is less than the current threshold. {1} This message is for informational purposes only. No action is required. perfalert.pool.threadsLowCpuLow=TUNE0303W: Number of threads working in {0} is low, but the system does not seem to be under stress. {1} The CPU utilization of this system is unusually low. Run the performance advisor with a representative workload. If CPU utilization is expected to be this low, consider decreasing the size of the thread pool. If not, the bottleneck might exist elsewhere in the system, preventing work from reaching the Application Server. To decrease the size of the thread pool For the Web container, click Servers > Application Servers > server > Thread Pools in the administrative console. To decrease the size of the thread pool for the ORB Service, click Servers > Application Servers > server > Container Services > ORB Service > Thread Pool. cfgAlert.jvmConfig.maxHeapTooBig=TUNE5004W: The JVM maximum heap size is unusually large. Typically, the maximum heap size is no more than {0}. If the heap size is too large for the amount of physical memory on your machine, your system might page and degrade performance. If this situation occurs, you might reduce your application footprint or add physical memory to your system. perfalert.memory=TUNE0216W: There is not enough memory to change settings. {0} An alert was issued recommending a setting increase. However, the Java Virtual Machine (JVM) heap might not have enough memory to implement the change. Consider changing the JVM heap size, the time that is spent in garbage collection, and the memory usage. To change the JVM heap size, open the administrative console and click Application Servers > Server > Java and Process Management > Process Definition > Java Virtual Machine. perfalert.session.writeSizeTooLarge=TUNE0211W: The sessions being written to the session repository for {0} are unusually large. {1} Large sessions can reduce performance. The major costs are serialization, communication with the repository and the amount of memory used. Consider revising your application to reduce the session size. perfalert.session.CacheSmallEnough=TUNE0309I: The ratio of live sessions and session cache size is small enough that resources are not wasted. {0} This message is for informational purposes only. No action is required. perfalert.connPool.poolSizeGreaterThanMin=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} The current algorithm only decreases the minimum or maximum pool size settings if the current pool size is equal to the MinPoolSize setting. No action is required. cfgAlert.jvmConfig.maxHeapTooSmall=TUNE5003W: The JVM maximum heap size is unusually small. Typically, the maximum heap size is greater than or equal to {0}. If the maximum heap size is too small, the Java Virtual Machine (JVM) does not have enough room to manage the heap efficiently. Performance degrades and the application can fail. To change the JVM heap size, open the administrative console and click Application Servers > server > Java and Process Management > Process Definition > Java Virtual Machine. See the information center for more information on tuning JVM. perfalert.session.CacheRatioGood=TUNE0307I: The session cache ratio of (live sessions)/(session cache size) is good. {0} This message is for informational purposes only. No action is required. perfalert.inValidPoolSize=TUNE0316I: The size of the {0} is invalid. The pool size is {1}; there are {2} active threads. {3} Either the thread pool size is negative or the number of active threads is greater than the thread pool size. Check your thread pool settings in the administrative console: For the Web container, click Servers > Application Servers > server > Thread Pools. For the ORB Service, click Servers > Application Servers > server > Container Services > ORB Service > Thread Pool. cfgAlert.jvmConfig.JITDisabled=TUNE5006W: The JIT is disabled on the JVM. {0} Having the JIT disabled will reduce performance of the Application Server. To change the JVM heap size, open the administrative console and click Application Servers > server > Java and Process Management > Process Definition > Java Virtual Machine. See the information center for more information on tuning JVM. perfalert.session.writeSizeOk=TUNE0310I: The size of the session objects written by the application server, for {0} are within reasonable limits. {1} This message is for informational purposes only. No action is required. perfalert.Exception.NotificationClassCastException=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} This is an internal system error. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . perfalert.prepStmt.message_increase=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} Caching all prepared statements improves performance. In general, the size of the cache must equal the number of prepared statements that are used in the application. To increase the size of the prepared statement cache in the administrative console, click Resources > JDBC Providers > JDBC_provider > Data sources > data_source and increase the value in Statement Cache Size field. Refer to the information center for more information about tuning data source connection pools. perfalert.memoryLeak.warning=TUNE9005I: The following suspious memory warning has been detected. {0}. Memory usage patterns have indicated a potential problem No action is required cfgAlert.orb.minGreaterThanMax=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} The value that is specified for the minimum thread pool of the Object Request Broker (ORB) is greater than the value for the maximum thread pool. To change the size of the thread pool, open the administrative console and click Servers > Application Servers > server > Container Services > ORB Service > Thread Pool. See the information center for more information on tuning your Application Server. perfalert.memoryLeak.noProblem=TUNE9004I: No memory leak detected {0}. Memory usage patterns do not indicate a memory leak No action is required perfalert.noData=TUNE0318I: There is no data available for data point {0}. If the problem persists, check the Performance Monitoring Infrastructure (PMI) settings. {1} The Runtime Performance Advisor enables this data point for future use. No action is required. cfgAlert.jvmConfig.initialHeapTooBig=TUNE5002W: The JVM initial heap size is unusually large. Typically, the initial heap size is no more than {0}. If the minimum heap size is too large, the Java Virtual machine (JVM) cannot reduce the heap to an appropriate size. Garbage collection takes more time, which causes longer interruptions in application processing. To change the JVM heap size, open the administrative console and click Application Servers > server > Java and Process Management > Process Definition > Java Virtual Machine. See the information center for more information on tuning JVM. perfalert.Exception.AttributeNotFound=TUNE0404E: Runtime Performance Advisor could not find the attribute {0} on mbean {1} This is an internal system error. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . perfalert.noInterval=TUNE0321W: Not enough data to perform analysis. {0} The Runtime Performance Advisor, advice or Performance Monitoring Infrastructure (PMI) data point might have been enabled. No action is required. perfalert.connPool.tooSmall=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} The connection pool might be unnecessarily limiting the performance of your system. Increasing the size of the pool can also reduce performance. Test carefully. You can obtain optimal performance when the connection pool is large enough to support full cpu utilization. In general, expect to see high utilization of the thread pool. To change the size of connection pool, open the administrative console and click Resources > JDBC Providers > JDBC_provider > Data Sources > data_source > Connection pool properties. cfgAlert.webContainer.minGreaterThanMax=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} The value specified for the minimum thread pool of the Web container is greater than the value for the maximum thread pool. To change the size of the thread pool, open the administrative console and click Servers > Application Servers > server > Thread Pools. See the information center for more information on tuning your Application Server. perf.tuning.session.size.notNeeded=TUNE0224W: Consider lowering the monitoring level from Maximum to High for the modules listed below. {0} The performance advisor does not need the "PMI monitored statistic set" to be "all". Lower the PMI monitored statistic set to extended. perfalert.session.readTimeTooLarge=TUNE0212W: Reading persistent sessions is unusually slow for {0}. {1} Your session repository might have a problem or your sessions might be too large. If you use multi-row sessions, the times are per attribute, rather than per session. Consult the application provider about reducing the session size. perfalert.session.CacheLargeEnough=TUNE0308I: The session cache for {0} is large enough to contain the average number of live sessions. {1}. This message is for informational purposes only. No action is required. perfalert.memoryLeak.canceled=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} To provide early notification of a suspicious memory activity short and long data collection periods are used. Sometimes a short period issues a notification which is later determined to be false when looking at the larger amount of data contained within a long period. No action is required cfgAlert.orb.maxSizeTooBig=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} In general, a very large thread pool reduces performance, although it might be necessary for some applications. To change the size of the thread pool, open the administrative console and click Servers > Application Servers > server > Container Services > ORB Service > Thread Pool. See the information center for more information on tuning your Application Server. cfgAlert.configRule.errorReadingConfig=TUNE5901W: An error occurred while reading the configuration for {0}. {1} An error occurred reading the configuration through the configuration service or configuration data is not in the log file, if in log replay mode. No action is required. cfgAlert.orb.minSizeTooBig=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} In general, a very large thread pool reduces performance, although it might be necessary for some applications. To change the size of the thread pool, open the administrative console and click: Servers > Application Servers > server > Container Services > ORB Service > Thread Pool. See the information center for more information on tuning your Application Server. perfalert.Exception.couldNotRegisterForNotification.mBeanServerDelegate=TUNE0405E: Runtime Performance Advisor could not register for regisration/unregistration notifications on the MBeanServerDelegate for type {0}. The error reported was {1}. The Runtime Performance Advisor failed to register for notifications of runtime changes. If you are running in network deployment environment, make sure that the deployment manager is still running. cfgAlert.connPoolConfig.useDB2TuningWizard=TUNE5035W: Run the DB2 Performance Configuration Wizard for advice on tuning DB2 databases for performance. The DB2 Performance Configuration Wizard calculates and suggests configuration parameters to optimize the performance of your DB2 database. To access the DB2 Performance Configuration Wizard, right click the database object in the DB2 Control Center and select Configure Performance Using Wizard. perfalert.memoryLeak.unboundedHeap.memoryLeakDetected=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}. A memory leak might cause the size of the java process to grow in an unbounded manner. Either adjust the memory pool size or use tooling to further analyze your memory useage over time. Refer to the information center for more information about diagnosing out-of memory errors and java heap memory leaks. perfalert.error=TUNE0323W: There was a general error detected in the Runtime Performance Advisor. Check the application server logs. {0} The Runtime Performance Advisor created an error. Locate the log files under the installation root > logs directory. Each server instance has its own directory in the logs directory. Enable tracing in the administrative console by clicking Application Servers > server > Logging and Tracing > Diagnostic Trace Service. cfgAlert.connPoolConfig.minPoolSizeTooBig=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} In general, a very large connection pool reduces performance, although it might be necessary for some applications. To change the connection pool properties, open the administrative console and click JDBC Providers > JDBC_provider > Data Sources > data_source > Connection pool properties. See the information center for more information about queueing. perfalert.session.readTimeOk=TUNE0312I: The time taken to read session objects is reasonable for {0}. {1} This message is for informational purposes only. No action is required. perfalert.pool.cpuLow=TUNE0305I: Since the CPU is heavily utilized, increasing the number of threads in {0} does not improve performance. {0} This message is for informational purposes only. No action is required. perfalert.Exception=TUNE0410E: There was a general error detected in the Runtime Performance Advisor. Check the application server logs. {0} The Runtime Performance Advisor created an error. Each server instance has its own directory in the logs directory. Enable the com.ibm.ws.performance.tuning.serverAlert.*=all=enabled tracing in the administrative console by clicking Application Servers > server > Logging and Tracing > Diagnostic Trace Service. perfalert.noProblem=TUNE0317I: No further tuning problems have been found. {0} The performance advisor limits the number of times a particular warning is issued. A tuning problem can still exist, even though no more messages are issued. No action is required. cfgAlert.webContainer.maxSizeTooBig=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} In general, a very large thread pool reduces performance, although it might be necessary for some applications. To change the size of the thread pool, open the administrative console, click: Servers > Application Servers > server > Thread Pools. See the information center for more information on tuning your Application Server. cfgAlert.webContainer.minSizeTooBig=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} In general, a very large thread pool reduces performance, although it might be necessary for some applications. To change the size of the thread pool, open the administrative console and click Servers > Application Servers > server > Thread Pools. See the information center for more information on tuning your Application Server. perfalert.memoryLeak.memoryLeakDetected=TUNE9001W: Heap utilization patterns indicate that you may have a memory leak {0}. Over a period of time the amount of free memory appears to be decreasing or there is consistently insufficient free memory in the heap, indicating that you may have a memory leak. Use tooling to further analyze your memory usage over time. Refer to the information center for more informationabout diagnosing out-of-memory errors and java heap memory leak. perfalert.pool.tooManyThreads=TUNE0203W: Based on the number of processors, the {0} thread pool is unusually large. {1} If this message appears repeatedly, look for continued growth of the thread pool, which often indicates a leak or deadlock. This message might also indicate a temporary load surge. However, if the thread pool remains steadily at this size, the large number of threads might degrade performance. Test a bounded thread pool of a smaller size. To change the thread pool size for the Web container in the administrative console, click Servers > Application Servers > server > Thread Pools. To change the thread pool size for the ORB Service, click Servers > Application Servers > server > Container Services > ORB Service > Thread Pool.