From torque-dev-return-5035-apmail-db-torque-dev-archive=db.apache.org@db.apache.org Tue Feb 08 09:05:53 2005 Return-Path: Delivered-To: apmail-db-torque-dev-archive@www.apache.org Received: (qmail 69897 invoked from network); 8 Feb 2005 09:05:49 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 8 Feb 2005 09:05:49 -0000 Received: (qmail 24849 invoked by uid 500); 8 Feb 2005 09:05:39 -0000 Delivered-To: apmail-db-torque-dev-archive@db.apache.org Received: (qmail 24828 invoked by uid 500); 8 Feb 2005 09:05:39 -0000 Mailing-List: contact torque-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Apache Torque Developers List" Reply-To: "Apache Torque Developers List" Delivered-To: mailing list torque-dev@db.apache.org Received: (qmail 21420 invoked by uid 500); 8 Feb 2005 09:03:03 -0000 X-ASF-Spam-Status: No, hits=2.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,FORGED_YAHOO_RCVD X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=CYnRGlnTd8zjEWM/SBi888JGcnNEXxUrVm/AjITX+jX0hp4s6nkOsUdqH1hGCHrqhZbJph/Oft/XP9Ii+CnwUcJArCBv3xkPB0r/83uqKxPZiV8z74s3+/JMea+S6UJhXgAJb8HbKtyUVujeL8NCnee/oIbu2dO5kfWG6va1AFo= ; Message-ID: <20050208090258.69021.qmail@web90104.mail.scd.yahoo.com> Date: Tue, 8 Feb 2005 01:02:58 -0800 (PST) From: Junino Julius Subject: Question To: db-torque-cvs@apache.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N There are situations in which the database is loaded, and throws Exceptions because of this load. I'm using mysql and there is a retry mechasim there that tries to query the database again when Exceptions are thrown. In this stage, the retry mechasim is making sure the database is killed, since it just increases the load. On the other hand, removing the retry mechanism totally is unwise, since the database throws an exception from time to time, and with the retry the data is resolved. Is there any way to prevent this situation using the torque cache? Anyone else had this problem, and might have a solution. __________________________________ Do you Yahoo!? All your favorites on one personal page – Try My Yahoo! http://my.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org For additional commands, e-mail: torque-dev-help@db.apache.org