A common cause of performance problems is when request handling threads get hung up waiting for a database connection from a database that has become unresponsive. Since the MonitoredDataSource extends the atg.service.resourcepool.ResourcePool class, it inherits the ResourcePool’s properties that handle these situations. The creationTimeLimit and maxPendingCreations properties can disable a ResourcePool if the pool is unable to create new connections. For more information about these properties, see the Core Dynamo Services chapter of the ATG Programming Guide.

If you stop and then restart your database, use the invalidateAllResources() method of atg.service.resourcepool to invalidate any defunct connections in your pool. This method runs through the list of all resources-both inside and outside of the pool-and flags them as invalid. Note: If you start and stop your database or if your database shuts down and is restarted for any reason, all of the connections in your connection pool will be defunct.

 
loading table of contents...