Awesome, works great. Now to figure out how to fix these incorrect statements...
______________________ Shawn Haworth LWSI/WebDev Programmer Siegfried Goeschl <[EMAIL PROTECTED]> 03/22/2006 10:35 AM Please respond to "Turbine Users List" <[email protected]> To Turbine Users List <[email protected]> cc Subject Re: SQL Query Logging / Debugging Mhmm, not sure it this folder is in the classpath - could you move it to WEB-INF/classes Siegfried Goeschl [EMAIL PROTECTED] wrote: > Yes, my spy.properties is located in WEB-INF/conf.. I have that exact > entry in it also. I can connect to the database fine normally, but when I > change the default connection driver to: > torque.dsfactory.default.connection.driver = > com.p6spy.engine.spy.P6SpyDriver > > I get null exceptions. > > > ______________________ > Shawn Haworth > LWSI/WebDev Programmer > 501.558.4619 401.744.5337 > > > > Siegfried Goeschl <[EMAIL PROTECTED]> > 03/22/2006 09:14 AM > Please respond to > "Turbine Users List" <[email protected]> > > > To > Turbine Users List <[email protected]> > cc > > Subject > Re: SQL Query Logging / Debugging > > > > > > > Hi Shawn, > > just double-checking > > +) do you have a spy.properties in your classpath > +) does it contain "realdriver=com.ibm.as400.access.AS400JDBCDriver" > > Cheers, > > Siegfried Goeschl > > [EMAIL PROTECTED] wrote: > >>Ok I followed your instructions on the wiki. I still can't seem to get > > it > >>running. My Torque.properties looks like this: >> >>torque.database.default=default >>torque.database.default.adapter=db2app >>torque.database.default.adapter=db2400 >> >>##torque.dsfactory.default.connection.driver = >>com.ibm.as400.access.AS400JDBCDriver >>torque.dsfactory.default.connection.driver = >>com.p6spy.engine.spy.P6SpyDriver >>torque.dsfactory.default.connection.url = >>jdbc:as400://<serverip>;libraries=LWPSML >>torque.dsfactory.default.connection.user = username >>torque.dsfactory.default.connection.password = password >> > > torque.dsfactory.default.factory=org.apache.torque.dsfactory.TorqueDataSourceFactory > >>Still getting a null pointer, further examination of the jetspeed.log > > file > >>shows that there's "No Datasource Configured for connection default". >> >> >>______________________ >>Shawn Haworth >>LWSI/WebDev Programmer >>501.558.4619 401.744.5337 >> >> >> >>Siegfried Goeschl <[EMAIL PROTECTED]> >>03/22/2006 08:32 AM >>Please respond to >>"Turbine Users List" <[email protected]> >> >> >>To >>Turbine Users List <[email protected]> >>cc >> >>Subject >>Re: SQL Query Logging / Debugging >> >> >> >> >> >> >>Hi Shawn, >> >>currently I work on non-Turbine application but I got P6Spy running with >> >>+) Turbine/Tomcat >>+) BEA WebLogic with EJBs >>+) my current contracting job based on RESIN with a custom connection > > pool > >>The following link might help in Turbine land >> >> > > http://wiki.apache.org/db-torque/FrequentlyAskedQuestions#head-46f663e01bea72682fdc5f60ae02f2a47de29fec > > >> >>Cheers, >> >>Siegfried Goeschl >> >>[EMAIL PROTECTED] wrote: >> >> >>>Great, thanks for the idea. I'm trying to configure this for Tomcat 5, >>>unfortunately their instructions on the site are outdated (version 3.x). > > >> >>>Which webserver are you using? >>> >>> >>>______________________ >>>Shawn Haworth >>>LWSI/WebDev Programmer >>>501.558.4619 401.744.5337 >>> >>> >>> >>>Siegfried Goeschl <[EMAIL PROTECTED]> >>>03/22/2006 06:20 AM >>>Please respond to >>>"Turbine Users List" <[email protected]> >>> >>> >>>To >>>Turbine Users List <[email protected]> >>>cc >>> >>>Subject >>>Re: SQL Query Logging / Debugging >>> >>> >>> >>> >>> >>> >>>Hi Shawn, >>> >>>I use a different approach using (in a different context) >>> >>>+) P6Spy as JDBC proxy driver >>>+) Log4J to write the P6SPY logs to a SocketAppender >>>+) SQLProfiler (http://www.jahia.net/jahia/page597.html) which visualize > > >> >>>the JDBC access >>> >>>This week it helped me to trace an escaping problem related to the JDBC >>>driver internals ... :-) >>> >>>Cheers, >>> >>>Siegfried Goeschl >>> >>>[EMAIL PROTECTED] wrote: >>> >>> >>> >>>>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 >>> >>> >>>--------------------------------------------------------------------- >>>To unsubscribe, e-mail: [EMAIL PROTECTED] >>>For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >>> >>> >> >> >>--------------------------------------------------------------------- >>To unsubscribe, e-mail: [EMAIL PROTECTED] >>For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
