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 184.108.40.206 and 220.127.116.11 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
- 15 Seconds : Advanced UI Design Using XML and XSL - Part 1: Folder Tree Creation
- as400 Iseries Tips
- NadaBlog: Building An Effects Pedal Board
- What is QZHQSSRV job?
- AS400 APIs
- apachefriends.org - very easy apache, mysql, php and perl installation without hassles
- Using QCLRDTAQ to clear data queues in CL and RPG
- AS400 API - QCMDEXC - Execute Command