[jira] Updated: (DIRSERVER-667) Logging level settings ignored in apachedsw.exe windows NT service frontend (apachedsw.exe)

["Alex Karasulu (JIRA)" <ji...@apache.org>]

     [ http://issues.apache.org/jira/browse/DIRSERVER-667?page=all ]

Alex Karasulu updated DIRSERVER-667:
------------------------------------

    Attachment: log4j.properties

Log4j configuration file for using an additional appender instead of relying on stdout to dump logs properly.  Comment to follow for workaround in a little bit.

> Logging level settings ignored in apachedsw.exe windows NT service frontend (apachedsw.exe)
> -------------------------------------------------------------------------------------------
>
>                 Key: DIRSERVER-667
>                 URL: http://issues.apache.org/jira/browse/DIRSERVER-667
>             Project: Directory ApacheDS
>          Issue Type: Bug
>    Affects Versions: 1.0-RC3
>         Environment: Win2k JDK 1.5-06
>            Reporter: Alain Pannetier
>         Assigned To: Alex Karasulu
>            Priority: Critical
>         Attachments: log4j.properties
>
>
> apachedsw.exe appears to ignore the requested settings for logging level.
> How to reproduce 
> 1 - run %apacheds_home%\bin\apachedsw.exe
> 2 - In the "Logging" tab from the level combo, select Debug
> 3 - In the log prefix type test_debug.log
> 4 - in the log path set sth such as : C:\tmp\log
> 5 - In the Redirect stdout type C:\tmp\log\apacheds-stdout.log
> 6 - In the Redirect stderr type C:\tmp\log\apacheds-stderr.log
> 7 - Click on "Apply" and restart service.
> Perform some typical LDAP requests
> Have a look at the files in C:\tmp\log\
> All the expected files are there.  None have any debug log entry...
> I can possibly help if told where to look.
> Thanks.

-- 
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