Redhat 7.7 will break the systemd interaction with Artifactory

When doing a yum update we get to the latest version, released around 24hrs ago, rhel 7.7.

Whether we install Artifactory before updating into 7.7, or if we install Artifactory after going into rhel 7.7 we get the same behavior. Artifactory will start successfully but the pid file will not be found as it is quickly removed.

Artifactory is still running just fine, but systemd believes it is not as there is no PID file.

Aug 08 01:06:34 instance-12 systemd[1]: Can't open PID file /tmp/artifactory.pid (yet?) after start: No such file or directory
Aug 08 01:06:34 instance-12 systemd[1]: Failed to start Setup Systemd script for Artifactory in Tomcat Servlet Engine.
Aug 08 01:06:34 instance-12 systemd[1]: Unit artifactory.service entered failed state.
Aug 08 01:06:34 instance-12 systemd[1]: artifactory.service failed.

I was not able to create an artifactory.pid file in /var/opt/jfrog/run, but I was able to change the path to /tmp/ and create the file (this time not being deleted). The file was recognized by the status command and seemed that the system was fine. However, as soon as I stopped and tried to start the system again we went back to the same behavior.

This was reproduce with permissive, disabled, and enforced policies on SELinux. 

Open files count for both root and artifactory user were under the defined ulimit

The release notes for this version of RHEL indicate that systemd was updated.