Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@forrest.apache.org
Message-ID: <802904449.1133862068789.JavaMail.jira@ajax.apache.org>
Date: Tue, 6 Dec 2005 10:41:08 +0100 (CET)
From: "Ross Gardler (JIRA)" <jira@apache.org>
To: dev@forrest.apache.org
Subject: [jira] Commented: (FOR-702) Improve logging from Locationmap
In-Reply-To: <1237488566.1128478667492.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/FOR-702?page=comments#action_12359394 ] 

Ross Gardler commented on FOR-702:
----------------------------------

Yeah, I've been working on it periodically as I work on Locationmaps. Basically, if I find a problem I can't solve I add logging.

I've not found such a problem for a while, so maybe this issue can be closed, but not yet...

Right now the locatonmap logs are being duplicated in the linkrewriter, the locationmap and the core logs. This is a waste of resources, we need to make them appear in just the locationmap log. I guess this is a logkit.xconf setting

> Improve logging from Locationmap
> --------------------------------
>
>          Key: FOR-702
>          URL: http://issues.apache.org/jira/browse/FOR-702
>      Project: Forrest
>         Type: Improvement
>   Components: Locationmap
>     Reporter: Ross Gardler
>      Fix For: 0.8-dev

>
> Debugging locationmaps is currently very difficult as no log information is provided.
> We need the following debug log entries:
> - for matches - record all entries encountered
> - for select statements, record all entries being tested

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira