Return-Path: Delivered-To: apmail-db-ojb-dev-archive@www.apache.org Received: (qmail 39693 invoked from network); 25 Sep 2008 14:48:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 25 Sep 2008 14:48:30 -0000 Received: (qmail 19595 invoked by uid 500); 25 Sep 2008 14:48:27 -0000 Delivered-To: apmail-db-ojb-dev-archive@db.apache.org Received: (qmail 19559 invoked by uid 500); 25 Sep 2008 14:48:27 -0000 Mailing-List: contact ojb-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "OJB Developers List" Reply-To: "OJB Developers List" Delivered-To: mailing list ojb-dev@db.apache.org Received: (qmail 19546 invoked by uid 99); 25 Sep 2008 14:48:27 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Sep 2008 07:48:27 -0700 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Sep 2008 14:47:27 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1Kis8O-00039w-7N for ojb-dev@db.apache.org; Thu, 25 Sep 2008 07:48:00 -0700 Message-ID: <19671098.post@talk.nabble.com> Date: Thu, 25 Sep 2008 07:48:00 -0700 (PDT) From: Jenish To: ojb-dev@db.apache.org Subject: Problems while using OJB with iAnywhere Driver to connect Sybase MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: jenish.shah@gmail.com X-Virus-Checked: Checked by ClamAV on apache.org Hello All, We have a project which uses OJB to talk with DB. It was working fine with jconnect driver. Now we have changed our design and now we are trying iAnywhere driver instead of jConnect2. Now we are facing the problem that after some time of deployment we are getting exception at the backend something like "Borrow broker from pool failed" Can anybody please suggest me if we need to tune some parameter of OJB to make it run with iAnywhere? Thanks, Jenish -- View this message in context: http://www.nabble.com/Problems-while-using-OJB-with-iAnywhere-Driver-to-connect-Sybase-tp19671098p19671098.html Sent from the Apache DB - ObjectRelationalBridge Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org For additional commands, e-mail: ojb-dev-help@db.apache.org