Welp, I've resolved my problem by uncommenting the Jdbc2Pool and commenting the Torque old pool in the Torque.properties file.
> -----Original Message----- > From: Mark Lybarger > Sent: Monday, March 03, 2003 12:58 PM > To: 'Turbine Users List' > Subject: RE: null connection object > > > Thanks for the response! > > I'm not asking torque for a connection, I'm asking a peer > class to return a > OM class instance. I put a try /catch around the second > database call, > and still no list of objects was returned. > > I've specified the idMethod="idbroker" for all my tables, but > I do not want > to rely on turbine to generate the primary keys. the user > gets to enter > those. i'll take away the idbroker piece and see what happends there. > > I'm still interested in how/why the torque would have a null > connection > after a failed SQL call, and not be able to recover from it > right away? It > does recover if i attempt a search again, then it gets a good > connection. > > > -----Original Message----- > > From: Eric Emminger [mailto:[EMAIL PROTECTED] > > Sent: Monday, March 03, 2003 12:20 PM > > To: Turbine Users List > > Subject: Re: null connection object > > > > > > Mark > > > > It's possible, although I'm not sure and could be very wrong, > > that when > > Torque throws that exception, it also returns the connection > > to the pool. > > > > What id method are you using on that table? I'm guessing > you're using > > "none" since you are supplying the pk that's giving you the > > first exception. > > > > Eric > > > > > I'm using the TDK 2.2.01 and have it working with my oracle > > database and > > > velocity templates. My trouble is that when i try to > > insert a record that > > > already exists (pk violation), an exception is thrown. i > > can catch the > > > exception, but when i try to call select on the peer, the > > connection object > > > is null and an exception is thrown there. > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: > [EMAIL PROTECTED] > > > > --- > > Incoming mail is certified Virus Free. > > Checked by AVG anti-virus system (http://www.grisoft.com). > > Version: 6.0.455 / Virus Database: 255 - Release Date: 2/13/2003 > > > > > > --- > Outgoing mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.455 / Virus Database: 255 - Release Date: 2/13/2003 > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --- > Incoming mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.455 / Virus Database: 255 - Release Date: 2/13/2003 > > --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.455 / Virus Database: 255 - Release Date: 2/13/2003 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
