Yeah, I know, I'm surprised too, but the SQL statments definitely don't show
up anywhere in the server log or the console output. I've gone through it
all very thoroughly. Some SQL must be being generated, since one of the
entity beans works fine. Yet none of it shows up in the debug.

Is there any other debug I can turn on, other than what I've already done:

- Adding <debug>true</debug> to jaws.xml
- Adding <debug>true</debug> to standardjaws.xml
- Setting <call-logging>true</call-logging> in standardjboss.xml (under
Standard CMP EntityBean, which is what I've written)
- Setting <attribute name="LoggingEnabled">true</attribute> for the
connection pool I'm using

Did I miss anything?

Thanks,
Jason

----- Original Message -----
From: K.V. Vinay Menon <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, May 11, 2001 2:35 PM
Subject: Re: [JBoss-user] CMP finder method problem


> Jason,
>     The sql statements should appear at server start up in the server log
if
> you set debug to true in the standardjaws file. They will come be logged
> just after the beans are deployed. Am surprised that it is not showing up.
> Is there any sql at all being generated?
>
> Vinay
> ----- Original Message -----
> From: "Jason Wells" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, May 11, 2001 9:11 PM
> Subject: Re: [JBoss-user] CMP finder method problem
>
>
> > I turned all this on, and although I do get additional debug printing
from
> > the datasource connection pool, I still get no SQL statements in either
> the
> > console output or in server.log.
> >
> > Any other ideas?
> >
> > ----- Original Message -----
> > From: <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Friday, May 11, 2001 1:07 AM
> > Subject: RE: [JBoss-user] CMP finder method problem
> >
> >
> > > > I could get to the bottom of this if I could just see what
> > > > the container is doing when the findAll() is triggered.
> > > > My question is: is there a way to print or log the SQL SELECT
> > > > statement that the container has executed on my entity bean's
> > > > behalf? If not, can anyone suggest a good way to debug
> > > > something like this?
> > >
> > > Yes, you can (there are few places where you can turn logging on and
> off):
> > >
> > > jaws.xml or standardjaws.xml and specify:
> > > <jaws>
> > >   ...
> > >   <debug>true</debug>
> > >   ...
> > > </jaws>
> > >
> > > jboss.xml or standardjboss.xml in you CMP container configuration:
> > >
> > > <!-- prints the method invoked by container -->
> > > <call-logging>true</call-logging>
> > >
> > > in jboss.jcml in your datasource configuration:
> > >
> > > <mbean ...>
> > >   ...
> > >   <attribute name="LoggingEnabled">true</attribute>
> > > </mbean>
> > >
> > >
> > > Also, do not forget to watch the server.log, not the console output,
> > because
> > > SQL statements appear only in server log (at least in my case).
> > >
> > > Roman
> > >
> > > _______________________________________________
> > > JBoss-user mailing list
> > > [EMAIL PROTECTED]
> > > http://lists.sourceforge.net/lists/listinfo/jboss-user
> >
> >
> > _______________________________________________
> > JBoss-user mailing list
> > [EMAIL PROTECTED]
> > http://lists.sourceforge.net/lists/listinfo/jboss-user
>
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user


_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to