Applications that connect to a back-end server and that have become slow or unresponsive might be encountering connection problems that are related to the application code or configuration problems, rather than to bugs in the WebSphere� connection manager. These issues include leaked connections that are not explicitly closed by application, and connectionWaitTimeoutExceptions in the application that might fill up the connection pool without returning connections to the free pool.
The Connection Manager code for WebSphere versions 220.127.116.11 and 18.104.22.168 provides a new diagnostic feature, connection leak trace logic, that gathers information on which application methods might be generating leaked connections, or might be holding on to connections for longer than expected. This information is useful, especially considering that connections should not take much longer then the maximum processing time of the longest running query in the application.
Thursday, April 20, 2006
- Yahoo! Mail: Revenge of the Oddpost
- Creating an as400 Query
- Javalobby - Java J2EE Programming Forums - Coldtags suite 2.1: 210+ custom JSP tags
- Free Iseries Accounts Available
- How do you re-enable the user id for STRSST when it has been disabled?
- Other as400 tips sites
- Differences between iseries as400 API QMHLJOBL and QGYOLJBL
- AS400 PRTF - Report Layout Utility
- as400 Iseries Tips
- Automating a process to run every 10 minutes