Hi,

Unfortunatelly setting the priority to ERROR will not solve the
problem. Driver will still generate tons of log messages, they will
simply not appear in log. This is very expensive in terms of CPU and
memory, so you'd better switch logging off (it should be off by
default, but you can force it with -DFBLog4j=false). Any error
condition will result in SQLException, so you can be sure that you do
not miss anything.

Roman.

--- In Firebird-Java@y..., "William L. Thomson Jr." <support@o...> wrote:
> You need to modify the prop file in the jar file in the rar file.
>
> It's should be the first line or two and changed DEBUG to ERROR or
> FATAL. They can be all caps or all lower case.
>
> Although in conjunction with that I usually use another prop file for
> each app. See a past from Roman Rokytskyy on the 16 Jul 2002.
>
> I asked basically the same question, but in a different context. I
> wanted the logging.
>
> I would assume it to be better at first to remain debug and then adjust
> it from there for your needs. As you may have problems during initial
> deployment. At which time you will have enough to deal with much less
> changing the setting. But it is really a mood issue, no?
>
>
>
> On Wed, 2002-07-17 at 15:57, Todd Jonker wrote:
> > Thanks Roman.
> >
> > It appears that the (JCA) driver is logging tons of stuff by
default. At
> > least it's doing so when I drop the RAR into JBoss.
> >
> > Personally, I think the default should be to log at the ERROR level or
> > worse.
> >
> > How do I go about changing the log level for *just* the driver?
The only
> > messages I've found in the archive seem like they would affect the
entire
> > application, not just the driver components. Is this even possible?
> >
> > (Sorry if this is a dumb question; I'm a newbie to both Jboss and
log4j.
> > Perhaps the answer can be added to the release notes.)
> >
> > Thanks,
> >
> > .T.
> >
> >
> > On 7/16/02 5:50 PM, rrokytskyy@y... wrote:
> >
> > > Hi,
> > >
> > > I have fixed a bug in org.firebirdsql.logging.LoggerFactory.
> > > Implementation tried to look for org.apache.log4j.Logger class
that is
> > > not available in log4j version shipped with driver. Also our
> > > org.firebirdsql.logging.Log4jLogger uses org.apache.log4j.Category,
> > > and not org.apache.log4j.Logger.
> > >
> > > Now you can specify -DFBLog4j=true and get extensive logging in
> > > log/test.log file.
> > >
> > > Best regards,
> > > Roman Rokytskyy
> >
> > --
> > Love does not consist in gazing at each other, but in looking outward
> > together in the same direction. -- Antoine de Saint-Exupery
> >
> >
> >
> > To unsubscribe from this group, send an email to:
> > Firebird-Java-unsubscribe@y...
> >
> >
> >
> > Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/
> >
> >
> --
> Sincerely,
> William L. Thomson Jr.
> Support Group
> Obsidian-Studios Inc.
> 439 Amber Way
> Petaluma, Ca. 94952
> Phone 707.766.9509
> Fax 707.766.8989
> http://www.obsidian-studios.com