I understand that's how you setup the SQL query logging, thank you for the confirmation. The problem I'm having is that it's not working. I don't know if it has to do with the type of database I'm using (DB2/AS400) but there are no entries with regards to SQL at all in jetspeed.log
I'm trying to debug an issue with the Torque/Turbine framework interfacing with a DB2 environment. It appears that many of the prepared statements aren't compatible with the V5R3 system. PS.. cc'd the dev list on this one. If anyone on that list has an answer or suggestion, please cc me directly. Thanks. ______________________ Shawn Haworth LWSI/WebDev Programmer "Shabada, Gnaneshwer" <[EMAIL PROTECTED]> 03/21/2006 05:23 PM Please respond to "Jetspeed Users List" <[email protected]> To 'Jetspeed Users List' <[email protected]> cc Subject RE: SQL Query Logging / Debugging yes, thats how you configure your log files. You can also write your own Customer logger to roll out the log file every day/week/month based on your activity.. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 21, 2006 1:50 PM To: [email protected]; [email protected] Subject: SQL Query Logging / Debugging Hi all, I'm trying to facilitate the SQL queries called by Jetspeed. In the TRP, I setup log4j to do so.. but I still don't see the queries or errors. I know I'm getting an error because I get an SQL exception when logging in (i'm using the DB2/400 as a test database). Here's my entry in TRP: services.LoggingService.system.destination.file=/WEB-INF/log/jetspeed.log services.LoggingService.system.className=org.apache.turbine.services.logging .FileLogger services.LoggingService.system.level=DEBUG >From what I've read this should be good enough to send the queries to jetspeed.log. Anyone else encounter this or know another approach? ______________________ Shawn Haworth LWSI/WebDev Programmer ======================================================================== This email message is for the sole use of the intended recipient (s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. To reply to our email administrator directly, send an email to [EMAIL PROTECTED] Toys "R" Us, Inc. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
