Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <24152889.1187235083223.JavaMail.jira@brutus>
Date: Wed, 15 Aug 2007 20:31:23 -0700 (PDT)
From: "Adrian Co (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Commented: (AMQ-1363) activemq/conf/log4j.properties does
 not seem to get recognized
In-Reply-To: <6391280.1187187143022.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/activemq/browse/AMQ-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39945 ] 

Adrian Co commented on AMQ-1363:
--------------------------------

I tried both on a windows and a linux machine, and the debug logging seems to work ok.

Though I did disabled the specific threshold being used by the console logger, so it will use the general threshold, specified at the start. Not sure, if this was the cause why you weren't seeing any debug info. :)

> activemq/conf/log4j.properties does not seem to get recognized
> --------------------------------------------------------------
>
>                 Key: AMQ-1363
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1363
>             Project: ActiveMQ
>          Issue Type: Bug
>            Reporter: James Strachan
>            Assignee: Adrian Co
>
> Try taking a binary build; enabling debug logging by editing activemq/conf/log4j.properties, then rerunning the broker. I get no change!
> BTW I've patched the activemq-core-*-tests.jar to not include a log4j.properties file. Also I tried adding the activemq/conf directory explicitly in the console - to no avail.
> I also tried zapping the activeio jars and grepping the jars to see if any had any included log4j.properties files - to no avail

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.