Mark and Linus,
On 12/11/25 2:28 AM, Mark Thomas wrote:
On 10/12/2025 21:58, Linus Kamb wrote:
Mark,
Thanks very much for your response.
The disk is local, not shared.
So given the statement "... the disk from which all the tomcats run ..."
does this mean we are talking about multiple Tomcat instances running on
a single physical machine? Or something else?
Are any files shared between the instances?
How is the web application deployed? WAR file that Tomcat then expands?
I want to make sure I understand the architecture before I spend too
much time thinking about what might be going on.
Could the fact that there was no space left on the disk be treated as
being unavailable?
Seems unlikely. Tomcat has a list of files it checks for each webapp and
looks to see if the modification time has changed.
And why only the one webapp? Perhaps because it was the one
attempting to
write to the disk?
Again, seems unlikely.
Might some external process changed the last modification time on any
files? A back-up process maybe? Those times should not be sensitive to
clock / time zone changes but I'd check if there were any changes of
that nature just in case.
+1
Is the web application configured to auto-reload? Tomcat will watch more
than just the timestamp on the application's deployment directory for
changes. There are other files that can cause a reload. (But generally
not a re-deployment.)
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
