WebSphere Performance Auto-tuning Support messages |
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}
Explanation:
If the system is meant to be under load, there may be a bottleneck within the application itself ( such as over synchronization ), or elsewhere in the system. If this problem occurs in a test environment, the load driver may have reached its maximum limit.
User Response:
Consult the WebSphere Application Server InfoCenter for information on deadlocks and application performance tuning.
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}
Explanation:
Caching all prepared statements typically improves performance. In general, the size of the cache should equal the number of prepared statements used in the application.
User Response:
From the administrative console, click: JDBC Providers > JDBC_provider > Data Sources > data_source and increase the Statement Cache Size field.
TUNE0202W: Increasing the {0} thread pool''s Maximum Size to {1} may improve performance. {2}
Explanation:
When a growable thread pool expands beyond the maximum size, those additional threads will not be reused and will 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.
User Response:
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.
Consult the WebSphere Application Server InfoCenter for information on deadlocks.
TUNE0203W: Based on the number of processors, the {0} thread pool is unusually large. {1}
Explanation:
If this message appears repeatedly, look for continued growth of the thread pool, which often indicates a leak or deadlock. This message may also indicate a temporary load surge. However, if the thread pool remains steadily at this size, then the large number of threads may hurt performance. Consider testing a bounded thread pool of a smaller size.
User Response:
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.
Consult the WebSphere Application Server InfoCenter for information on deadlocks.
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}
Explanation:
The CPU utilization of the system is high. Decreasing the size of the thread pool will free resources and may improve performance.
User Response:
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.
TUNE0205W: Increasing the {0} by setting the minimum size to {1} and the maximum size to {2} may improve performance. {3}
Explanation:
The utilization of the thread pool is high, yet the CPU utilization is low. It is possible that the thread pool size is too small, and might be unnecessarily limiting the performance of your system. WARNING: Increasing the size of the pool can also hurt performance. Test carefully. Optimal performance is usually obtained when the thread pool size is just large enough to support full CPU utilization. It is normal to see high utilization of the thread pool.
User Response:
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.
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}
Explanation:
Decreasing the size supports better pooling and frees memory resources.
User Response:
From the administrative console, click: Resources > JDBC Providers > JDBC_provider > Data Sources > data_source > Connection pool properties.
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}
Explanation:
It is possible that the connection pool is unnecessarily limiting the performance of your system. WARNING: Increasing the size of the pool can also hurt performance. Test carefully. Optimal performance is usually obtained when the connection pool is just large enough. In general, expect to see high utilization of the thread pool.
User Response:
From the administrative console, click: Resources > JDBC Providers > JDBC_provider > Data Sources > data_source > Connection pool properties.
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}
Explanation:
The system appears to be under load (CPU is very busy,) yet the number of threads used within the pool is small. Decreasing the size of the thread pool will free resources and may improve performance.
User Response:
From the administrative console, click: Resources > JDBC Providers > JDBC_provider > Data Sources > data_source > Connection pool properties.
TUNE0210W: Writing persistent sessions is unusually slow for {0}. {1}
Explanation:
There might be a problem with your session repository, 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 above are per attribute, rather than per session.
User Response:
Consult the application provider about reducing the session size.
TUNE0211W: The sessions being written to the session repository for {0} are unusually large. {1}
Explanation:
Large sessions can hurt 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.
User Response:
Consult the application provider about reducing the session size.
TUNE0212W: Reading persistent sessions is unusually slow for {0}. {1}
Explanation:
There might be a problem with your session repository, or your sessions might be too large. If you use multi-row sessions, the times above are per attribute, rather than per session.
User Response:
Consult the application provider about reducing the session size.
TUNE0213W: The sessions being read by {0} from the session repository are unusually large. {1}
Explanation:
Large sessions can hurt 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.
User Response:
Consult the application provider about reducing the session size.
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}
Explanation:
In this situation, the overflow session cache is used instead of the main session cache, possibly hurting 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.
User Response:
From the administrative console, click: Servers > Application Servers > Server > Web Container Settings > Web Container > Session Management.
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}
Explanation:
When the session cache is full and can not overflow, getSession will 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 will result in a memory leak.
User Response:
From the administrative console, click: Servers > Application Servers > Server > Web Container Settings > Web Container > Session Management.
TUNE0216W: There is not enough memory to change settings. {0}
Explanation:
An alert was issued recommending a setting increase. However there is not enough memory available in the JVM heap to implement the change. Consider changing the JVM heap size, the time spent in garbage collection and the memory usage.
User Response:
From the administrative console, click: Application Servers > Server > Java and Process Management > Process Definition > Java Virtual Machine.
TUNE0217E: Unknown data type. {0}
Explanation:
Data access is not available for this data type.
User Response:
See the Troubleshooting section of the InfoCenter.
TUNE0218W: The dynamic cache instance {0} is not large enough to store all cacheable results. Consider increasing the number of cache entries to {1}.
Explanation:
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.
User Response:
From the administrative console, click: Servers > Application Servers > Server > Container Services > Dynamic Cache Service.
TUNE0219W: The dynamic cache instance {0} is not currently using all the available entries. Consider decreasing the number of cache entries to {1}.
Explanation:
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.
User Response:
From the administrative console, click: Servers > Application Servers > Server > Container Services > Dynamic Cache Service.
TUNE0220W: The Java virtual machine is spending a considerable amount of time in garbage collection. Consider increasing the heap size. {0}
Explanation:
There are many reasons why an application may 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 JVM's memory manager to thrash. Increasing the heap size will help in this case, by lengthening the time between garbage collection calls, but will also increase the time needed for each garbage collection.
User Response:
From the administrative console, click: Application Servers > Server > Java and Process Management > Process Definition > Java Virtual Machine.
TUNE0221W: Data for memory session size is not available for certain Web applications. {0}
Explanation:
Session size contributes to application performance. If the data is available, the performance advisor can give advice on the average session size.
User Response:
Enable the PMI counter Session Object Size if not using distributed sessions.
TUNE0222W: The sessions in the session cache of Web application {0} average {1}K, which is unusually large. {2}
Explanation:
Large sessions can hurt performance. The major costs are serialization, and the amount of memory used. Consider revising your application to reduce the average session size.
User Response:
Contact the application developer about decreasing the average session size.
TUNE0223W: There is at least one session in the session cache of Web application {0} which is {1}K. {2}
Explanation:
Large sessions can hurt performance. The major costs are serialization, and the amount of memory used. Consider revising your application to reduce the maximum session size.
User Response:
Contact the application developer about decreasing the maximum session size.
TUNE0224W: Consider lowering the monitoring level from Maximum to High for the modules listed below. {0}
Explanation:
The performance advisor does not need the "PMI monitored statistic set" to be "all". Lowering the "PMI monitored statistic set" to "extended" can provide additional performance boost.
User Response:
If other applications are not using this PMI data, then consider lowering the "PMI monitored statistic set" to "extended".
TUNE0301W: The percent of connections used in the connection pool is optimal. {0}
Explanation:
The connection pool size is fine and the pool usage is good.
User Response:
No action is required.
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}
Explanation:
The current algorithm only decreases the Minimum/Maximum Pool Size settings if the current pool size is equal to the MinPoolSize setting.
User Response:
No action is required.
TUNE0303W: Number of threads working in {0} is low, but the system does not seem to be under stress. {1}
Explanation:
The CPU utilization of this system is unusually low. Please run the performance advisor with a representative workload. If CPU utilization is expected to be this low, then consider decreasing the size of the thread pool. If not, the bottleneck may exist elsewhere in the system, preventing work from reaching the WebSphere Application Server.
User Response:
To decrease the size of the thread pool: 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.
TUNE0304I: No problem detected with the {0}. {1}
Explanation:
Connection pool size looks good.
User Response:
No action is required.
TUNE0305I: Since the CPU is heavily utilized, increasing the number of threads in {0} does not improve performance. {0}
Explanation:
The CPU is already heavily utilized. Increasing the number of threads in the pool increases the time spent switching between threads.
User Response:
No action is required.
TUNE0306I: The current average thread pool size: {0} is less than the current threshold. {1}
Explanation:
The current thread pool size is less than the maximum defined size.
User Response:
No action is required.
TUNE0307I: The session cache ratio of (live sessions)/(session cache size) is good. {0}
Explanation:
The session cache size is well configured.
User Response:
No action is required.
TUNE0308I: The session cache for {0} is large enough to contain the average number of live sessions. {1}.
Explanation:
The session cache has enough entries to store the average number of live sessions.
User Response:
No action is required.
TUNE0309I: The ratio of live sessions and session cache size is small enough that resources are not wasted. {0}
Explanation:
The session cache size is small enough that resources are not wasted.
User Response:
No action is required.
TUNE0310I: The size of the session objects written by the application server, for {0} are within reasonable limits. {1}
Explanation:
The size of the session objects written to the persistent store is within reasonable limits.
User Response:
No action is required.
TUNE0311I: The size of the persistent store session objects that are read by the application server for {0} are within reasonable limits. {1}
Explanation:
The size of the session objects read from the persistent store is within reasonable limits.
User Response:
No action is required.
TUNE0312I: The time taken to read session objects is reasonable for {0}. {1}
Explanation:
Reading large sessions can cause serious performance problems.
User Response:
No action is required.
TUNE0313I: The time taken to write session objects for {0} is reasonable. {1}
Explanation:
Writing large sessions can cause serious performance problems.
User Response:
No action is required.
TUNE0314I: In the current interval, there is room available in session cache for new sessions of Web Application {0}. {1}
Explanation:
Session cache size looks good.
User Response:
No action is required.
TUNE0315I: The prepared statement cache is set appropriately for data source {0}. {1}
Explanation:
The size of the prepared statement cache is set appropriately.
User Response:
No action is required.
TUNE0316I: The size of the {0} is invalid. The pool size is {1}; there are {2} active threads. {3}
Explanation:
Either the thread pool size is negative, or the number of active threads is greater than the thread pool size.
User Response:
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
TUNE0317I: No further tuning problems have been found. {0}
Explanation:
Remember that 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.
User Response:
No action is required.
TUNE0318I: There is no data available for data point {0}. If the problem persists, check the Performance Monitoring Infrastructure (PMI) settings. {1}
Explanation:
The Runtime Performance Advisor enables this data point for future use.
User Response:
From the administrative console, click: Application Servers > Server > Performance Monitoring Infrastructure (PMI).
Note: Setting the JVM module to all requires enabling the Java Virtual Machine Profiling Interface (JVMPI). See the InfoCenter for more on this topic.
TUNE0319W: Unable to completely utilize the performance advisor because data collection is not enabled for some modules. Enable monitoring for the specified modules. {0}
Explanation:
To fully utilize the performance advisor, enable monitoring for these modules.
User Response:
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 InfoCenter for more on this topic.
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}
Explanation:
The Performance Monitoring Infrastructure (PMI) is not enabled for this server.
User Response:
From the administrative console, click: Application Servers > Server > Performance Monitoring Infrastructure (PMI). Enable the Performance Monitoring Infrastructure (PMI) and restart the server.
TUNE0321W: Not enough data to perform analysis. {0}
Explanation:
The Runtime Performance Advisor, advice, or Performance Monitoring Infrastructure (PMI) data point might have just been enabled.
User Response:
No action is required.
TUNE0322W: The Runtime Performance Advisor is not running. Restart the application server. {0}
Explanation:
To use the Runtime Performance Advisor, restart the application server.
User Response:
From the WebSphere Application Server installation directory, go to the bin directory and type stopserver.bat to stop the server and then type startserver.bat to start the server.
TUNE0323W: There was a general error detected in the Runtime Performance Advisor. Check the application server logs. {0}
Explanation:
A general error was detected.
User Response:
Locate the logs for WebSphere Application Server, in the logs directory, under the installation root 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.
TUNE0324W: There was an unknown error detected in the Runtime Performance Advisor. Check the application server logs and enable trace. {0}
Explanation:
An unknown error was detected.
User Response:
Locate the logs for WebSphere Application Server, in the logs directory, under the installation root 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.
TUNE0325I: Enough dynamic cache entries are allocated. {0}
Explanation:
There are no problems with the number of dynamic cache entries allocated.
User Response:
No action is required.
TUNE0326I: There are no problems with the amount of time spent garbage collecting. {0}
Explanation:
The Java virtual machine is spending a reasonable amount of time garbage collecting.
User Response:
No action is required.
TUNE0327I: There are no problems with the in-memory session size. {0}
Explanation:
The in-memory session sizes are all reasonable.
User Response:
No action is required.
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}
Explanation:
The Performance Monitoring Infrastructure (PMI) is not enabled for this nodeagent.
User Response:
From the administrative console, click: System Administration > Node Agents > nodeagent > Performance Monitoring Infrastructure (PMI). Enable the Performance Monitoring Infrastructure (PMI) and restart the nodeagent.
TUNE0401E: There was an exception getting an AdminClient {0}.
Explanation:
Performance Runtime Advisor expected to get an admin client and did not.
User Response:
Check that Node Agent is running and that process discovery has occurred on the application server.
TUNE0402E: Runtime Performance Advisor could not register for notifications for {0}. The error reported was {1}.
Explanation:
The Runtime Performance Advisor registers for notifications of runtime changes. For some reason it was unable to do so.
User Response:
If running in ND please make sure that the Deployment Manager is still running
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}
Explanation:
Internal WebSphere error
User Response:
Contact support
TUNE0404E: Runtime Performance Advisor could not find the attribute {0} on mbean {1}
Explanation:
Internal WebSphere error
User Response:
Contact support
TUNE0405E: Runtime Performance Advisor could not register for regisration/unregistration notifications on the MBeanServerDelegate for type {0}. The error reported was {1}.
Explanation:
The Runtime Performance Advisor registers for notifications of runtime changes. For some reason it was unable to do so.
User Response:
If running in ND please make sure that the Deployment Manager is still running
TUNE0406E: The attribute {0} is not available from the mbean {1}. The Runtime Performance Advisor will use the repository configuration in it's place.
Explanation:
The Runtime Peformance Advisor uses the runtime settings in order to help determine performance problems. This data was not available so that persistent configuration will be used instead of the runtime configuration.
User Response:
None
TUNE0407E: Could not refresh repository cache .
Explanation:
There was a problem getting the Application Server Configuration details from the Repository.
User Response:
Please contact IBM support.
TUNE0408E: Could not refresh {0} Configuration.
Explanation:
There was a problem getting the Application Server Session Configuration details from the Repository.
User Response:
Please contact IBM support.
TUNE0409E: could not get {0} resource from config root.
Explanation:
There was a problem getting the Resource from the config root.
User Response:
Please contact IBM support.
TUNE0410E: There was a general error detected in the Runtime Performance Advisor. Check the application server logs. {0}
Explanation:
A general error was detected.
User Response:
Locate the logs for WebSphere Application Server, in the logs directory, under the installation root directory. Each server instance has its own directory in the logs directory. Enable com.ibm.ws.performance.tuning.serverAlert.*=all=enabled tracing in the administrative console, by clicking: Application Servers > Server > Logging and Tracing > Diagnostic Trace Service.
TUNE0999W: Encountered an error while running performance advisor. {0}
Explanation:
An error occurred while running performance advisor.
User Response:
Restart performance advisor.
TUNE5001W: JVM initial heap size is unusually small. Typically, the initial heap size is greater than or equal to {0}.
Explanation:
If the initial JVM heap size is too small, the heap has to expand more often than desired, reducing performance when the application server is first initialized.
User Response:
From the administrative console, click: Application Servers > Server > Java and Process Management > Process Definition > Java Virtual Machine.
TUNE5002W: The JVM initial heap size is unusually large. Typically, the initial heap size is no more than {0}.
Explanation:
If the minimum heap size is too large, the JVM cannot reduce the heap to an appropriate size. Garbage collection takes more time, causing longer interruptions in application processing.
User Response:
From the administrative console, click: Application Servers > Server > Java and Process Management > Process Definition > Java Virtual Machine.
TUNE5003W: The JVM maximum heap size is unusually small. Typically, the maximum heap size is greater than or equal to {0}.
Explanation:
If the maximum heap size is too small, the JVM does not have enough room to manage the heap efficiently. Performance degrades, and the application can fail.
User Response:
From the administrative console, click: Application Servers > Server > Java and Process Management > Process Definition > Java Virtual Machine.
TUNE5004W: The JVM maximum heap size is unusually large. Typically, the maximum heap size is no more than {0}.
Explanation:
If the heap size is too large for the amount of physical memory on your machine, then your system will page, reducing performance. Monitor your system. If this situation occurs, attempt to reduce your application footprint or add physical memory to your system.
User Response:
From the administrative console, click: Application Servers > Server > Java and Process Management > Process Definition > Java Virtual Machine.
TUNE5005W: The initial JVM heap size is greater than the maximum heap size. {0}
Explanation:
The JVM heap size settings specify an initial heap size that is larger than the maximum heap size.
User Response:
From the administrative console, click: Application Servers > Server > Java and Process Management > Process Definition > Java Virtual Machine.
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}
Explanation:
The value specified for the minimum thread pool of the Web container is greater than the value for the maximum thread pool.
User Response:
From the administrative console, click: Servers > Application Servers > Server > Thread Pools.
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}
Explanation:
In general, a very large thread pool hurts performance, although it might be necessary for some applications. See the WebSphere Application Server Tuning Guide for more information.
User Response:
From the administrative console, click: Servers > Application Servers > Server > Thread Pools.
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}
Explanation:
In general, a very large thread pool hurts performance, although it might be necessary for some applications. See the WebSphere Application Server Tuning Guide for more information.
User Response:
From the administrative console, click: Servers > Application Servers > Server > Thread Pools.
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}
Explanation:
The value specified for the minimum thread pool of the ORB is greater than the value for the maximum thread pool.
User Response:
From the administrative console, click: Servers > Application Servers > Server > Container Services > ORB Service > Thread Pool.
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}
Explanation:
In general, a very large thread pool hurts performance, although it might be necessary for some applications. See the WebSphere Application Server Tuning Guide for more information.
User Response:
From the administrative console, click: Servers > Application Servers > Server > Container Services > ORB Service > Thread Pool.
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}
Explanation:
In general, a very large thread pool hurts performance, although it might be necessary for some applications. See the WebSphere Application Server Tuning Guide for more information.
User Response:
From the administrative console, click: Servers > Application Servers > Server > Container Services > ORB Service > Thread Pool.
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}
Explanation:
The value specified for the minimum connection pool of the data source is greater than the maximum pool size.
User Response:
From the administrative console, click: JDBC Providers > JDBC_provider > Data Sources > data_source > Connection pool properties.
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}
Explanation:
In general, a very large connection pool hurts performance, although it might be necessary for some applications. See the WebSphere Application Server Tuning Guide for more information.
User Response:
From the administrative console, click: JDBC Providers > JDBC_provider > Data Sources > data_source > Connection pool properties.
TUNE5033W: For data source {0}, the maximum connection pool size is unusually large. Typically, the connection pool size is no more than {1}. {2}
Explanation:
In general, a very large connection pool hurts performance, although it might be necessary for some applications. See the WebSphere Tuning Guide for more information.
User Response:
From the administrative console, click: JDBC Providers > JDBC_provider > Data Sources > data_source > Connection pool properties.
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}
Explanation:
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, which can be used more effectively. In general, the size of the cache equals the number of prepared statements used in the application.
User Response:
From the administrative console, click: JDBC Providers > JDBC_provider > Data Sources > data_source.
TUNE5035W: Run the DB2 Performance Configuration Wizard for advice on tuning DB2 databases for performance.
Explanation:
The DB2 Performance Configuration Wizard can calculate and suggest configuration parameters to optimize the performance of your DB2 database.
User Response:
To access the DB2 Performance Configuration Wizard, right click on the database object in the DB2 Control Center and select Configure Performance Using Wizard.
TUNE5041W: Enable dynamic caching for better performance. Enable dynamic caching using the administrative console. {0}
Explanation:
See the WebSphere Application Server InfoCenter for more information on using dynamic caching.
User Response:
From the administrative console, click: Servers > Application Servers > Server > Container Services > Dynamic Cache Service.
TUNE5042W: Enable servlet caching for better performance. {0}
Explanation:
See the WebSphere Application Server InfoCenter for more information on servlet caching.
User Response:
From the administrative console, click: Servers > Application Servers > Server > Web Container Settings > Web Container.
TUNE5901W: An error occurred while reading the configuration for {0}. {1}
Explanation:
An error occurred reading the configuration through the configuration service, or configuration data is not in the log file, if in log replay mode.
User Response:
none