Re: [pool][dbcp] instrumentation

2007-12-08 Thread Phil Steitz
On Dec 8, 2007 6:44 PM, sebb <[EMAIL PROTECTED]> wrote: > > On 20/11/2007, Phil Steitz <[EMAIL PROTECTED]> wrote: > > On Nov 20, 2007 2:30 AM, Jörg Schaible > > <[EMAIL PROTECTED]> wrote: > > > Phil Steitz wrote: > > > > On Nov 19, 2007 11:46 PM, Jörg Schaible > > > > <[EMAIL PROTECTED]> wrote: > >

Re: [pool][dbcp] instrumentation

2007-12-08 Thread sebb
On 20/11/2007, Phil Steitz <[EMAIL PROTECTED]> wrote: > On Nov 20, 2007 2:30 AM, Jörg Schaible > <[EMAIL PROTECTED]> wrote: > > Phil Steitz wrote: > > > On Nov 19, 2007 11:46 PM, Jörg Schaible > > > <[EMAIL PROTECTED]> wrote: > > >> > > >> Phil Steitz wrote: > > [snip] > > >>> Any other comments on

Re: [pool][dbcp] instrumentation

2007-11-20 Thread Phil Steitz
On 11/20/07, Noel J. Bergman <[EMAIL PROTECTED]> wrote: > Jörg Schaible wrote: > > Since the JUL loggers sit in the system class path, any formatter > > implementation *must* be available also in the system class path. > > Isn't this part of what JULI fixes? > >From the tomcat docs, looks like yes

RE: [pool][dbcp] instrumentation

2007-11-20 Thread Noel J. Bergman
Jörg Schaible wrote: > Since the JUL loggers sit in the system class path, any formatter > implementation *must* be available also in the system class path. Isn't this part of what JULI fixes? --- Noel - To unsubscribe

Re: [pool][dbcp] instrumentation

2007-11-20 Thread Phil Steitz
On Nov 20, 2007 2:30 AM, Jörg Schaible <[EMAIL PROTECTED]> wrote: > Phil Steitz wrote: > > On Nov 19, 2007 11:46 PM, Jörg Schaible > > <[EMAIL PROTECTED]> wrote: > >> > >> Phil Steitz wrote: > [snip] > >>> Any other comments on the naming, levels, use of JUL before I start? > >> > >> Why not using

RE: [pool][dbcp] instrumentation

2007-11-20 Thread Jörg Schaible
Phil Steitz wrote: > On Nov 19, 2007 11:46 PM, Jörg Schaible > <[EMAIL PROTECTED]> wrote: >> >> Phil Steitz wrote: [snip] >>> Any other comments on the naming, levels, use of JUL before I start? >> >> Why not using commons-logging? It supports trace level. JUL > is really a pain. It is applicable

Re: [pool][dbcp] instrumentation

2007-11-19 Thread Phil Steitz
On Nov 19, 2007 11:46 PM, Jörg Schaible <[EMAIL PROTECTED]> wrote: > > Phil Steitz wrote: > > On 11/19/07, Noel J. Bergman <[EMAIL PROTECTED]> wrote: > >> sebb wrote: > >> > >>> Phil Steitz <[EMAIL PROTECTED]> wrote: > I have been working on adding logging to pool and dbcp per previous >

RE: [pool][dbcp] instrumentation

2007-11-19 Thread Jörg Schaible
Phil Steitz wrote: > On 11/19/07, Noel J. Bergman <[EMAIL PROTECTED]> wrote: >> sebb wrote: >> >>> Phil Steitz <[EMAIL PROTECTED]> wrote: I have been working on adding logging to pool and dbcp per previous discussion here. I started with a partially instrumented version of pool 1.3

Re: [pool][dbcp] instrumentation

2007-11-19 Thread Phil Steitz
On 11/19/07, Noel J. Bergman <[EMAIL PROTECTED]> wrote: > sebb wrote: > > > Phil Steitz <[EMAIL PROTECTED]> wrote: > > > I have been working on adding logging to pool and dbcp per previous > > > discussion here. I started with a partially instrumented version of > > > pool 1.3 that I have been usi

RE: [pool][dbcp] instrumentation

2007-11-19 Thread Noel J. Bergman
sebb wrote: > Phil Steitz <[EMAIL PROTECTED]> wrote: > > I have been working on adding logging to pool and dbcp per previous > > discussion here. I started with a partially instrumented version of > > pool 1.3 that I have been using to investigate bug reports and test > > performance. I used jdk

Re: [pool][dbcp] instrumentation

2007-11-19 Thread sebb
On 19/11/2007, Phil Steitz <[EMAIL PROTECTED]> wrote: > I have been working on adding logging to pool and dbcp per previous > discussion here. I started with a partially instrumented version of > pool 1.3 that I have been using to investigate bug reports and test > performance. I used jdk logging

[pool][dbcp] instrumentation

2007-11-18 Thread Phil Steitz
I have been working on adding logging to pool and dbcp per previous discussion here. I started with a partially instrumented version of pool 1.3 that I have been using to investigate bug reports and test performance. I used jdk logging with the following guidelines * Finest (trace) level for det