[ 
https://issues.apache.org/jira/browse/DAEMON-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mark Thomas resolved DAEMON-474.
--------------------------------
    Fix Version/s: 1.5.0
                       (was: 1.3.4)
       Resolution: Fixed

> Logging doesn't work on 1.40./1.4.1 - Regression of 1.3.4 (worked perfectly)
> ----------------------------------------------------------------------------
>
>                 Key: DAEMON-474
>                 URL: https://issues.apache.org/jira/browse/DAEMON-474
>             Project: Commons Daemon
>          Issue Type: Bug
>          Components: prunsrv
>    Affects Versions: 1.4.0, 1.4.1
>         Environment: Windows Server 2022 (virtualized VMware) 
>            Reporter: kfeina
>            Priority: Major
>              Labels: logging
>             Fix For: 1.5.0
>
>         Attachments: TestService.zip
>
>
> Hello,
>  
> Building a windows servcie (exe mode), logging (StdOutput amd StdError) 
> doesn't work on 1.40./1.4.1. Both files are never initilizaed. 
>  
> With older version 1.3.4, StdOutput amd StdError were genreated. Files were 
> initializated and filled:  "Apache Commons Daemon procrun stdout/stderror 
> initialized."
>  
> I attach a small test with my results (StdOutput and StdError files are 0 
> bytes for 1.4x branch).
>  
> To reproduce, uncompress and locate everythig in C:\Temp :
>  
> Install_TestServices.bat
>  
> To test different versions change DAEMON_FOLDER variable:
> set "DAEMON_FOLDER=C:\Temp\commons-daemon-1.4.1-bin-windows" for
> set "DAEMON_FOLDER=C:\Temp\commons-daemon-1.3.4-bin-windows"
>  
> start/stop the service to test 
>  
> Please let me know if  you need more information. 
> Thanks a lot. 
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to