Your message dated Mon, 18 Oct 2021 11:24:16 +0200
with message-id <[email protected]>
and subject line Re: jetty9: RolloverFileOutputStream does not roll over
has caused the Debian Bug report #873695,
regarding jetty9: RolloverFileOutputStream does not roll over
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
873695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873695
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: jetty9
Version: 9.2.21-1~bpo8+1
Severity: normal
Dear Maintainer,
I have a problem jetty9 logging, the logs do not roll over at midnight and the
log file grows huge until jetty9 is restarted. This is exactly as in
https://github.com/eclipse/jetty.project/issues/1590. The only workaround I see
is to restart jetty9 with cron, but I want to avoid that (downtimes). Is it
possible to fix this in jessie-backports?
-- System Information:
Debian Release: 8.9
APT prefers oldstable-updates
APT policy: (990, 'oldstable-updates'), (990, 'oldstable'), (80,
'oldoldstable-updates'), (80, 'oldoldstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.82 (SMP w/6 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages jetty9 depends on:
ii adduser 3.113+nmu3
ii apache2-utils 2.4.10-10+deb8u10
ii default-jre-headless [java7-runtime-headless] 2:1.7-52
ii libjetty9-extra-java 9.2.21-1~bpo8+1
ii libjetty9-java 9.2.21-1~bpo8+1
ii openjdk-7-jre-headless [java7-runtime-headless] 7u151-2.6.11-1~deb8u1
Versions of packages jetty9 recommends:
pn authbind <none>
jetty9 suggests no packages.
-- Configuration Files:
/etc/default/jetty9 changed:
NO_START=0
VERBOSE=yes
JETTY_ARGS=jetty.port=8983
/etc/jetty9/jetty-logging.xml changed:
<?xml version="1.0"?>
<!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN"
"http://www.eclipse.org/jetty/configure_9_0.dtd";>
<!-- =============================================================== -->
<!-- Configure stderr and stdout to a Jetty rollover log file -->
<!-- this configuration file should be used in combination with -->
<!-- other configuration files. e.g. -->
<!-- java -jar start.jar etc/jetty-logging.xml -->
<!-- =============================================================== -->
<Configure id="logging" class="org.eclipse.jetty.util.log.Log">
<New id="ServerLog" class="java.io.PrintStream">
<Arg>
<New class="org.eclipse.jetty.util.RolloverFileOutputStream">
<Arg><Property name="jetty.logs"
default="./logs"/>/yyyy_mm_dd.out.log</Arg>
<Arg type="boolean">false</Arg>
<Arg type="int">90</Arg>
<Arg><Call class="java.util.TimeZone"
name="getTimeZone"><Arg>GMT</Arg></Call></Arg>
<Get id="ServerLogName" name="datedFilename"/>
</New>
</Arg>
</New>
<Get name="rootLogger">
<Call name="info"><Arg>Redirecting stderr/stdout to <Ref
refid="ServerLogName"/></Arg></Call>
</Get>
<Call class="java.lang.System" name="setErr"><Arg><Ref
refid="ServerLog"/></Arg></Call>
<Call class="java.lang.System" name="setOut"><Arg><Ref
refid="ServerLog"/></Arg></Call>
</Configure>
-- no debconf information
--- End Message ---
--- Begin Message ---
I am closing this issue because jessie and stretch-backports are no longer
supported and the problem was apparently fixed years ago.
Markus
signature.asc
Description: This is a digitally signed message part
--- End Message ---
__
This is the maintainer address of Debian's Java team
<https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-java-maintainers>.
Please use
[email protected] for discussions and questions.
