Re: Upgrade 2.3.2 to 2.3.3
Siegfried Goeschl <[email protected]> Thu, 25 Feb 2010 21:48:44 +0100
| Newsgroups | gmane.comp.jakarta.turbine.user |
|---|---|
| Organization | IT20one |
| Message-ID | <[email protected]> |
SELECT 1 FROM DUAL is the way to go for Oracle Siegfried Goeschl On 25.02.10 20:08, Thomas Vandahl wrote: > Chris Jölly wrote: >> Hi Juergen, >> >> the following versions: >> >> commons-dbcp-1.2.2.jar >> (which is in the Torque's distributions lib folder) >> >> commons-pool-1.4.jar (from Turbine 2.3.3 distributions lib folder) >> (but in Torque's distribution 1.3 is provided...) >> >> >> is Torque 3.3 not compatible with Turbine 2.3.3? > > It sure is. > >>>> 2010-02-23 13:43:59,765 WARN org.apache.torque.oid.IDBroker - Could >>> not read from connection Metadata whether transactions are supported >>> for the database aportalsapdb > > I guess this may lead you to more insight. Obviously the access to the > database is somehow screwed. You should try to get the Torque connection > working first. Turbine will follow suit. > > Did you ever use the Torque configuration you provided with Oracle? I'm > no Oracle crack but > > torque.defaults.pool.validationQuery = SELECT 1 > > should read > > torque.dsfactory.portaldb.pool.validationQuery = SELECT 1 FROM DUAL > > AFAIK. The same goes for the other pool-specific settings. > > Bye, Thomas. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >