[Mulgara-dev] debug messages

[Paul Gearon]

While trying to track this down I started wondering if this file was
related to the problem.  I didn't realize that it wasn't being loaded
into the jar file.

So, the problem here is due to a change *I* made.  :-}  However, the
log config isn't being tested, so I didn't realize I'd broken it.
Thanks Alex.

Paul

On Tue, Mar 25, 2008 at 3:42 PM, Alex Hall <alexhall at revelytix.com> wrote:
> I'm seeing the same symptoms.  It appears that the Log4J config file is
>  no longer included in the itql-1.1.x.jar file.  The build script that
>  creates this jar is looking for a file called log4j-itql.xml, which has
>  been removed from the conf directory.  Meanqhile, TqlSession.java
>  expects a config file called log4j-tql.xml; when it doesn't find it, it
>  falls back on the log4j BasicConfigurator which I suspect is sending
>  everything to stdout.
>
>  If you have the same problem I do, the first line you will see to stdout
>  when running the TQL shell is "Unable to find logging configuration
>  file...".  I think if you change the build.xml in src/jar/itql to use
>  log4j-tql.xml (as opposed to log4j-itql.xml) then this problem should be
>  resolved.
>
>  -Alex
>
>
>
>  Paul Gearon wrote:
>  > I'm trying to get a lot done, and I don't have time to spend an
>  > afternoon working out how this works, so I'm hoping someone here can
>  > tell me.....
>  >
>  > How can I configure log4j in Mulgara? Right now I have a fresh
>  > checkout sending debug messages to stdout for the TQL console. My
>  > reading of the config files says that I shouldn't have anything more
>  > detailed than an INFO message, though I wouldn't mind upping that to
>  > WARN. I've tried configure this in the past (every 6 months or so
>  > since 2002) and have never been able to make it work as documented.
>  > I've had people from Tucana stand over my shoulder and say, "You do it
>  > that way" only to discover that they were as uninformed as I was.
>  > Apparently Log4J docs are quite poor, or whoever set the configuration
>  > up didn't know what they were doing.
>  >
>  > I figure that someone out there must know what's going on, as I've
>  > never had DEBUG messages before, so someone must have checked
>  > something in.
>  >
>  > Any pointers on how to change this please?
>  >
>  > Paul
>
>
> > _______________________________________________
>  > Mulgara-dev mailing list
>  > Mulgara-dev at mulgara.org
>  > http://mulgara.org/mailman/listinfo/mulgara-dev
>  _______________________________________________
>  Mulgara-dev mailing list
>  Mulgara-dev at mulgara.org
>  http://mulgara.org/mailman/listinfo/mulgara-dev
>