| Explanation | |
| Action |
| Explanation | This is expected on non-Sun JVM environments |
| Action | None |
| Explanation | None |
| Action | None |
| Explanation | None |
| Action | None |
| Explanation | This is expected on non-Sun JVM environments |
| Action | None |
| Explanation | None |
| Action | None |
| Explanation | None |
| Action | None |
| Explanation | To prevent a memory leak, the JDBC Driver has been forcibly unregistered. |
| Action | To prevent this behavior please undo the automatic JDBC leak clearing configuration using wsadmin scripting or the administrative console. |
| Explanation | None |
| Action | None |
| Explanation | This is could potentially create a memory leak. |
| Action | None |
| Explanation | This is very likely to create a memory leak. |
| Action | Implement a cancellation policy that will take effect once the application is stopped. |
| Explanation | To prevent a memory leak, the timer (and the associated thread) has been forcibly canceled. |
| Action | To prevent this behavior undo the automatic timer thread stopping via wsadmin scripting or the administrative console. |
| Explanation | None |
| Action | None |
| Explanation | None |
| Action | None |
| Explanation | None |
| Action | None |
| Explanation | Threads are going to be renewed over time to try and avoid a probable memory leak. |
| Action | To prevent this behavior please undo the automatic thread pool renewal via wsadmin scripting or the administrative console. |
| Explanation | None |
| Action | None |
| Explanation | None |
| Action | None |
| Explanation | This is expected on non-Sun JVM environments. |
| Action | None |
| Explanation | None |
| Action | None |
| Explanation | None |
| Action | None |
| Explanation | None |
| Action | None |
| Explanation | None |
| Action | None |
| Explanation | None |
| Action | None |
| Explanation | None |
| Action | None |
| Explanation | None |
| Action | None |
| Explanation | None |
| Action | None |
| Explanation | None |
| Action | None |
| Explanation | None |
| Action | Please use a profiler to confirm the memory leak. |
| Explanation | None |
| Action | None |
| Explanation | None |
| Action | None |
| Explanation | None |
| Action | Enable Classloader leak detection by setting the com.ibm.ws.runtime.component.MemoryLeakConfig.detectAppCLLeaks JVM system property to true and restart the server. |
| Explanation | None |
| Action | Consider enabling Classloader leak fixing by setting the com.ibm.ws.runtime.component.MemoryLeakConfig.clearAppCLLeaks JVM system property to true and restarting the server. |
| Explanation | None |
| Action | None |
| Explanation | None |
| Action | Please stop the application [{0}]. |
| Explanation | None |
| Action | None |
| Explanation | None |
| Action | None |
| Explanation | None |
| Action | None |
| Explanation | Memory Leak Service runs only on application servers that host applications. |
| Action | Check if you are running the commands on the correct server or for any exceptions in the log. |
| Explanation | None |
| Action | None |