I would its' not its the database at all. Its between the database and coldfusion is where the problem is happening. Deep inside the JDBC pool as the error message clearly states. Sometimes error messages do tell the truth. Maintain Connections could be the problem. Sometimes its just better to allow the pool to do its work. The pool is just like a swimming pool and the water gets dirty and you need to start over with a fresh pool of water. This is an area CF 8 needs and needs badly is a way to view pooled conections and see if the connections are hanging around and not getting recycled as quickly as needed. And if each new connection gets blocked because backlog it will timeout. You can add proprieties to the JDBC string or add a proprieties file for CF to pickup or increase pooled connection size. Maybe then CF will time to recycle.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:260105 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
