tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Baktiar <dbakt...@gmail.com>
Subject Re: tomcat logs
Date Sat, 29 Dec 2018 09:06:27 GMT
Hi Adlet,

I have seen this problem many times. See if this ring a bell. This issue is
not specific to Tomcat, rather to processes running Linux/Unix file systems.

User run Tomcat in Linux/Unix. The server starts correctly, logging runs as
expected.
At some point in time, user decided to delete the log file while the Tomcat
is still running.
User expect a new log file will be created. Unfortunately the actual
behavior is Tomcat still holding to the file descriptor of the deleted
file. It won't create a new file as the user expected.
Restart Tomcat. A new log file will be created and logging behaves normally.

Moral of the story: do not delete log files while processes still opening
it in Linux/Unix and expects the file to be automatically created.

The behavior is different from on Windows, the default behavior of file
system, files will be locked exclusively by the process accessing it (this
behavior can of course be altered), and you won't be able to delete a log
file that is opened by Windows process.

Daniel


On Wed, Dec 19, 2018 at 4:52 PM Adlet Azhibek <adl.csse@gmail.com> wrote:

> 8.0.33 tomcat
> java Spring framework 4.3.13
> logging by "*org.slf4j.Logger*", "*org.slf4j.LoggerFactory*":
> example: *private final static Logger logger =
> LoggerFactory.getLogger(WebSocketController.class);*
>
>
> my logback-auction.xml:
> [image: grey — копия — копия.PNG]
> *logback-auction.xml* is located in classpath
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message