[Bug 1347864] New: The systemd service unit does not allow tomcat to shut down gracefully
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1347864
Bug ID: 1347864
Summary: The systemd service unit does not allow tomcat to shut
down gracefully
Product: Fedora
Version: 23
Component: tomcat
Assignee: ivan.afonichev(a)gmail.com
Reporter: csutherl(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: alee(a)redhat.com, csutherl(a)redhat.com,
ivan.afonichev(a)gmail.com,
java-sig-commits(a)lists.fedoraproject.org,
krzysztof.daniel(a)gmail.com, me(a)coolsvap.net,
tomcat-qe(a)redhat.com, trick(a)vanstaveren.us
Depends On: 1347860
+++ This bug was initially created as a clone of Bug #1347860 +++
Description of problem:
The systemd unit terminates the tomcat process prematurely, therefore not
allowing it to shutdown gracefully. The direct effect of this is that sessions
in the session manager are not persisted to disk and restored after a restart,
resulting in a loss of session data (unless you are replicating data within a
cluster).
Version-Release number of selected component (if applicable):
tomcat-8.0.32-5.fc23.noarch
How reproducible:
Always
Steps to Reproduce:
1. yum install tomcat
2. cp reproducer.war /usr/share/tomcat/webapps/
3. service tomcat start
4. curl http://localhost:8080/reproducer/getSession.jsp
5. service tomcat stop
6. ls /usr/share/tomcat/work/Catalina/localhost/reproducer/SESSIONS.ser
Actual results:
The session created by the curl request is not persisted into SESSIONS.ser.
Expected results:
The session created by the curl request is persisted to SESSIONS.ser
Additional info:
When the process successfully completes (with FINE logging on the
StandardManager (org.apache.catalina.session.StandardManager.level = FINE)),
you see the following along with other shutdown messages:
~~~
Jun 17, 2016 4:45:08 PM org.apache.catalina.session.StandardManager doUnload
FINE: Unloading persisted sessions
Jun 17, 2016 4:45:08 PM org.apache.catalina.session.StandardManager doUnload
FINE: Saving persisted sessions to SESSIONS.ser
Jun 17, 2016 4:45:08 PM org.apache.catalina.session.StandardManager doUnload
FINE: Unloading 4 sessions
Jun 17, 2016 4:45:08 PM org.apache.catalina.session.StandardManager doUnload
FINE: Expiring 4 persisted sessions
Jun 17, 2016 4:45:08 PM org.apache.catalina.session.StandardManager doUnload
FINE: Unloading complete
~~~
When you call the service stop, it terminates before the shutdown can complete
(almost immediately after calling stop):
~~~
INFO: Server startup in 3501 ms
Jun 17, 2016 4:58:20 PM org.apache.catalina.core.StandardServer await
INFO: A valid shutdown command was received via the shutdown port. Stopping the
Server instance.
Jun 17, 2016 4:58:20 PM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler ["http-bio-8080"]
~~~
--- Additional comment from Coty Sutherland on 2016-06-17 17:07:02 EDT ---
I'm able to get a graceful shutdown if I switch the unit type to Forking
instead of simple, but then the start hangs :(
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1347860
[Bug 1347860] The systemd service unit does not allow tomcat to shut down
gracefully
--
You are receiving this mail because:
You are on the CC list for the bug.
7 years, 9 months
[Bug 1341850] New: tomcat-jsvc.service has TOMCAT_USER value hard-coded
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1341850
Bug ID: 1341850
Summary: tomcat-jsvc.service has TOMCAT_USER value hard-coded
Product: Fedora
Version: 23
Component: tomcat
Assignee: ivan.afonichev(a)gmail.com
Reporter: csutherl(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: alee(a)redhat.com, csutherl(a)redhat.com,
ivan.afonichev(a)gmail.com,
java-sig-commits(a)lists.fedoraproject.org,
krzysztof.daniel(a)gmail.com, me(a)coolsvap.net
External Bug ID: Red Hat Bugzilla 1201409
Description of problem:
The TOMCAT_USER value should be configurable instead of always "tomcat".
Looking at the way that the service unit executes the tomcat script, I see that
the functions script is sourced in the preamble BEFORE the configuration is
loaded, so even if we check the TOMCAT_USER variable and try and use it, it
would always be empty. Could we move the configuration sourcing before we
source functions to make it configurable?
Version-Release number of selected component (if applicable):
tomcat-8.0.32-5.fc23.noarch
How reproducible:
Always
Steps to Reproduce:
1. Set TOMCAT_USER="notTomcat" in tomcat.conf
2. Start service with jsvc: systemctl start tomcat-jsvc
3. Observe that the process owner is "tomcat" instead of "notTomcat"
Actual results:
Process owner is "tomcat"
Expected results:
Process owner is "notTomcat"
Additional info:
This issue was raised against RHEL in the bug here
https://bugzilla.redhat.com/show_bug.cgi?id=1201409. I'll link it as well.
--
You are receiving this mail because:
You are on the CC list for the bug.
7 years, 9 months
[Bug 1343028] New: cal10n-0.8.1 is available
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1343028
Bug ID: 1343028
Summary: cal10n-0.8.1 is available
Product: Fedora
Version: rawhide
Component: cal10n
Assignee: mizdebsk(a)redhat.com
Reporter: puntogil(a)libero.it
QA Contact: extras-qa(a)fedoraproject.org
CC: java-sig-commits(a)lists.fedoraproject.org,
mizdebsk(a)redhat.com, msimacek(a)redhat.com
Latest upstream release: 0.8.1
Current version/release in rawhide: 0.7.7-8.fc25
URL: https://github.com/qos-ch/cal10n/tags
Please, considering upgrade
Required by wildfly 10+
--
You are receiving this mail because:
You are on the CC list for the bug.
7 years, 9 months
[Bug 998251] New: activemq 5.8.0 is available
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=998251
Bug ID: 998251
Summary: activemq 5.8.0 is available
Product: Fedora
Version: rawhide
Component: activemq
Assignee: mspaulding06(a)gmail.com
Reporter: puntogil(a)libero.it
QA Contact: extras-qa(a)fedoraproject.org
CC: agrimm(a)redhat.com,
java-sig-commits(a)lists.fedoraproject.org,
mspaulding06(a)gmail.com, tdawson(a)redhat.com
Created attachment 787792
--> https://bugzilla.redhat.com/attachment.cgi?id=787792&action=edit
update to 5.8.0
Upstream released activemq 5.8.0. Currently, we still have version 5.6.0 in
Rawhide. Please consider updating, patch is attached.
changes in spaec file
- update to 5.8.0
- built with XMvn
- adapt to current guideline
- obsoletes activemq-core activemq-kahadb
- built new modules:
° amq-store, broker, console, jdbc-store,
° log4j-appender, mqtt, openwire-generator,
° openwire-legacy, pool, ra, tooling
(ra module is required by Apache OpenEJB/Tomee 4.5.1)
- fix for CVE-2013-1879 (PATCH0)
- fix for rhbz#991956
NOTE some features cannot be avalaible, cause: require
com.thoughtworks.xstream:xstream:1.4.4
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=AN1TJhSLSq&a=cc_unsubscribe
7 years, 9 months
[Bug 1311950] New: CVE-2016-0792 jenkins: Remote code execution through remote API (SECURITY-247)
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1311950
Bug ID: 1311950
Summary: CVE-2016-0792 jenkins: Remote code execution through
remote API (SECURITY-247)
Product: Security Response
Component: vulnerability
Keywords: Security
Severity: high
Priority: high
Assignee: security-response-team(a)redhat.com
Reporter: anemec(a)redhat.com
CC: abhgupta(a)redhat.com, bleanhar(a)redhat.com,
ccoleman(a)redhat.com, dmcphers(a)redhat.com,
java-sig-commits(a)lists.fedoraproject.org,
jialiu(a)redhat.com, jkeck(a)redhat.com,
joelsmith(a)redhat.com, jokerman(a)redhat.com,
kseifried(a)redhat.com, lmeyer(a)redhat.com,
mizdebsk(a)redhat.com, mmccomas(a)redhat.com,
msrb(a)redhat.com, tiwillia(a)redhat.com
The following flaw was found in Jenkins:
Jenkins has several API endpoints that allow low-privilege users to POST XML
files that then get deserialized by Jenkins. Maliciously crafted XML files sent
to these API endpoints could result in arbitrary code execution.
External References:
https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+20...
--
You are receiving this mail because:
You are on the CC list for the bug.
7 years, 9 months
[Bug 1311949] New: CVE-2016-0791 jenkins: Non-constant time comparison of CSRF crumbs (SECURITY-245)
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1311949
Bug ID: 1311949
Summary: CVE-2016-0791 jenkins: Non-constant time comparison of
CSRF crumbs (SECURITY-245)
Product: Security Response
Component: vulnerability
Keywords: Security
Severity: medium
Priority: medium
Assignee: security-response-team(a)redhat.com
Reporter: anemec(a)redhat.com
CC: abhgupta(a)redhat.com, bleanhar(a)redhat.com,
ccoleman(a)redhat.com, dmcphers(a)redhat.com,
java-sig-commits(a)lists.fedoraproject.org,
jialiu(a)redhat.com, jkeck(a)redhat.com,
joelsmith(a)redhat.com, jokerman(a)redhat.com,
kseifried(a)redhat.com, lmeyer(a)redhat.com,
mizdebsk(a)redhat.com, mmccomas(a)redhat.com,
msrb(a)redhat.com, tiwillia(a)redhat.com
The following flaw was found in Jenkins:
The verification of user-provided CSRF crumbs with the expected value did not
use a constant-time comparison algorithm, potentially allowing attackers to use
statistical methods to determine valid CSRF crumbs using brute-force methods.
External References:
https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+20...
--
You are receiving this mail because:
You are on the CC list for the bug.
7 years, 9 months