In the Tomcat-based web interface for our CRM application product, we
have one customer running Tomcat on a WinDoze box (everybody else runs
it on the same AS/400 as the CRM application itself), and we have a log
file of our own, in <context>/logs, which is set to periodically close
the log file, give it a suffix, and start a new log file.
With most other installations, we see archived versions of our log file
going back for months. But in this one installation, the one running on
a WinDoze box, we only see the active log file and one archive.
There are no signs of any redeployments, and Tomcat's own log files go
back for months.
I've already asked our web interface people (who are in another
timezone) if they have any idea what (other than somebody going in and
manually deleting the archived logs) could be causing this, but is there
some Tomcat-specific reason why this would be happening?
--
James H. H. Lampert
Touchtone Corporation
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
