[logback-dev] [JIRA] Commented: (LBCORE-109) FileAppender writing to a shared (networked) file system

[Olivier Chartrel (JIRA)]

    [ http://jira.qos.ch/browse/LBCORE-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11319#action_11319 ] 

Olivier Chartrel commented on LBCORE-109:
-----------------------------------------

I am facing the same problem: Java application writing log files on a distant networked file system. If the network connection is lost and LogBack cannot write its log files, I would like to have an error written in my application server standard outpout.

I have made some tests: if I enable the "debug" mode for LogBack and network connection is down at application startup, I have an error written in my application server STDOUT.
But, if the network connection is  OK when application starts and the connection is lost later, LogBack does not write in log files any more but I don't have any error in my application server STDOUT... which is a problem in my case.

Is there a way to trace this kind of IO exception in application server's STDOUT (or STDERR) ?

> FileAppender writing to a shared (networked) file system
> --------------------------------------------------------
>
>                 Key: LBCORE-109
>                 URL: http://jira.qos.ch/browse/LBCORE-109
>             Project: logback-core
>          Issue Type: Bug
>    Affects Versions: 0.9.9, 0.9.10, 0.9.11, 0.9.12, 0.9.13, 0.9.14, 0.9.15
>            Reporter: Ceki Gulcu
>            Assignee: Ceki Gulcu
>
> FileAppender writing to a shared (networked) file system with lost networked connection.

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