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 Job Scheduler
- iReport - OpenSource Java Reporting Tool
- Java Examples - JExamples.com
- Using QCLRDTAQ to clear data queues in CL and RPG
- as400 commands and APIs you'll use for handling messages
- Creating an as400 Query
- Library list for Web server
- MobileTracker - Cingular announces EDGE Wireless WAN service
- How do you re-enable the user id for STRSST when it has been disabled?
- XMLHttpRequest & Ajax Working Examples - Links and Resources, Fiftyfoureleven.com
No comments:
Post a Comment