Loading...

XML

Word

Printable

Affects:

Release Notes
CDW devel_ack:
CDW docs_ack:
CDW pm_ack:
CDW qa_ack:
CDW release:
Release Note Text:

Hide
On Red Hat Enterprise Linux 7, the JBoss Web Server Tomcat 7 and 8 init scripts still use SysV units, which run in systemd compatibility mode.

In a future version of JBoss Web Server, these SysV init scripts will be replaced with systemd ones.

Show
On Red Hat Enterprise Linux 7, the JBoss Web Server Tomcat 7 and 8 init scripts still use SysV units, which run in systemd compatibility mode. In a future version of JBoss Web Server, these SysV init scripts will be replaced with systemd ones.
Release Note Status:
Documented as Known Issue
Target Release:

JWS 3.1.0 GA
Steps to Reproduce:
Hide

[root@machine system]# systemctl status tomcat7 tomcat7.service - LSB: start and stop tomcat Loaded: loaded (/etc/rc.d/init.d/tomcat7) Active: inactive (dead) [root@machine system]# systemctl status tomcat8 tomcat8.service - LSB: start and stop tomcat Loaded: loaded (/etc/rc.d/init.d/tomcat8) Active: inactive (dead)
Show
[root@machine system]# systemctl status tomcat7 tomcat7.service - LSB: start and stop tomcat Loaded: loaded (/etc/rc.d/init.d/tomcat7) Active: inactive (dead) [root@machine system]# systemctl status tomcat8 tomcat8.service - LSB: start and stop tomcat Loaded: loaded (/etc/rc.d/init.d/tomcat8) Active: inactive (dead)

As on RHEL7 SysV has been replaced by Systemd we should also replace existing init scripts for tomcat 7 and 8 on RHEL7 by systemd units.

Currently we are still using init scripts for Tomcat that work thanks to Systemd compatibility mode.

NOTE: httpd already has its own systemd unit - so fact that tomcat services still use init scripts is inconsistency which should be resolved

causes

JWS-666 [RHEL 7 RPM] TOMCAT_USER variable ignored

JWS-696 [RHEL 7 RPM] Tomcat needs sysconfig and conf files specific to systemd

is cloned by

JWS-1222 replace init scripts for tomcat7 and 8 on RHEL7 by systemd units