Logging stopped on a log file that I manually edit

[xsimo]

I'd like to know if that behavior is documented somewhere.

I've setup an AppenderRef with a MarkerFilter to intercept all log messages that have a specific Marker.

It worked well until when I opened the target file marker.log and edit it with vi.
Then, logging stopped to that marker.log file.

Could this be related to the operating system file handle or the pointer that the application has in that file ?

no error messages was seen in other general log file.

[ppkarwasz]

It worked well until when I opened the target file marker.log and edit it with vi. Then, logging stopped to that marker.log file.

Could this be related to the operating system file handle or the pointer that the application has in that file ?

This is caused by the way Vim writes changes to the current file:

• If backupcopy is set to yes, Vim will edit the content of the current file. Logging should continue without problems.
• If backupcopy is set to no, Vim will rename (and delete) the current file and create a new one in its place. The new file will have the same name, but a different inode number. Log4j will continue logging to the deleted file (the old inode).

If you want to edit log files, you need to call :set backupcopy=yes.
See Why does inode value change when we edit in "vi" editor for more details.