Cause
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.
Solution
The Connection Manager code for WebSphere versions 5.1.1.3 and 5.0.2.10 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
Subscribe to:
Post Comments (Atom)
Popular Posts
- as400 iSeries NetServer Disabled user profiles
- Create a Custom Live Linux CD - Leveraging BusyBox and OpenSSH
- Encode HTML Entities - Showing code in blogs
- Search for text in vi or vim
- Library list for Web server
- IBM eServer iSeries - iSeries NetServer: Command Line Setup
- Super $500 Myth Project
- HOW TO make a Powerbook in to a Wi-Fi access point!
- Reno County is preparing to move from an AS400 computer system to a personal-computer-based system
- QUSRJOBI API (Retrieve Job Information) as400
No comments:
Post a Comment