Martin,

Can you elaborate on this a bit?  Why does the change in location of 
spy.properties solve the problem?  Should deregister work on its own? 
Also, would a similar consideration apply if Tomcat is using a JDBC-based 
realm?  I've never had any luck getting p6spy to work with Tomcat, and 
this sounds like it might help - we don't use load-on-startup, but we do 
have JDBC realm.

thanks,
-steve

Steve Clark
ECOS Development Group
[EMAIL PROTECTED]
(970)226-9291




Martin Kal�n <[EMAIL PROTECTED]> 
05/18/2005 07:39 PM
Please respond to
"OJB Users List" <[email protected]>


To
OJB Users List <[email protected]>
cc

Subject
Re: P6Spy config






Charles Anthony wrote:
> Just a note on p6spy which may, or may not, be relevant : I've often had
> problems with processes finding the p6spy.properties file - it always 
seems
> to work for me if the file is in the "current" directory when the 
process
> starts.
> 
> So, for tomcat, for example, it seems to read the file from
> jakarta-tomcat-blah\bin
> 
> It *doesn't* seem to be read from the classpath.
> 
> This is not definitive, just something I recall from the dusty dank 
archives
> of my brain. Please treat with the appropriate amount of disdain.

Another catch-all failure of getting P6Spy to work under Tomcat is if
a servlet with load-on-startup=1 registers the standard JDBC driver
before the application/servlet with P6 is loaded.

In this scenario one has to make sure that spy.properties is in
CATALINA_HOME/common/classes and that p6spy.jar is in
CATALINA_HOME/common/lib (as opposed to WEB-INF/classes and
WEB-INF/lib respectively).

Then it's also important to have the deregister directive in 
spy.properties
set to "true" so that P6 first de-registers the already loaded JDBC driver
from DriverManager before registering it's own one.

I guess these pieces of info should be a good start for a FAQ entry some 
day. ;)

Cheers,
  Martin


---------------------------------------------------------------------
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]

Reply via email to